diff options
author | Alex Elder <elder@inktank.com> | 2013-02-16 17:07:32 +0000 |
---|---|---|
committer | Sage Weil <sage@inktank.com> | 2013-05-01 21:16:22 -0700 |
commit | 3a42b6c43e4ef65d0edd7d9e5c4366002b4e951d (patch) | |
tree | 7f3284055df4a6b1b6d7ff7e044703535a7e6c3f /Documentation/IRQ-domain.txt | |
parent | cf7b7e1492e97dd0c44479239742eb4cb752eeed (diff) |
ceph: simplify ceph_sync_write() page_align calculation
(This is being reposted. The first one had a problem because it
erroneously added a similar change elsewhere; that change has been
dropped.)
The next patch in this series points out that the calculation for
the number of pages in an osd request is getting done twice. It
is not obvious, but the result of both calculations is identical.
This patch simplifies one of them--as a separate step--to make
it clear that the transformation in the next patch is valid.
In ceph_sync_write() there is some magic that computes page_align
for an osd request. But a little analysis shows it can be
simplified.
First, we have:
io_align = pos & ~PAGE_MASK;
which is used here:
page_align = (pos - io_align + buf_align) & ~PAGE_MASK;
Note (pos - io_align) simply rounds "pos" down to the nearest multiple
of the page size.
We also have:
buf_align = (unsigned long)data & ~PAGE_MASK;
Adding buf_align to that rounded-down "pos" value will stay within
the same page; the result will just be offset by the page offset for
the "data" pointer. The final mask therefore leaves just the value
of "buf_align".
One more simplification. Note that the result of calc_pages_for()
is invariant of which page the offset starts in--the only thing that
matters is the offset within the starting page. We will have
put the proper page offset to use into "page_align", so just use
that in calculating num_pages.
This resolves:
http://tracker.ceph.com/issues/4166
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Diffstat (limited to 'Documentation/IRQ-domain.txt')
0 files changed, 0 insertions, 0 deletions