From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com, bo.li.liu@oracle.com,
dsterba@suse.cz, chandan@mykolab.com, quwenruo@cn.fujitsu.com
Subject: Re: [PATCH V2 02/11] Btrfs: Compute and look up csums based on sectorsized blocks
Date: Sun, 09 Aug 2015 17:17:13 +0530 [thread overview]
Message-ID: <1909720.tCRSQLki4e@localhost.localdomain> (raw)
In-Reply-To: <55C4F93D.3010605@fb.com>
On Friday 07 Aug 2015 14:30:21 Josef Bacik wrote:
> On 08/07/2015 03:05 AM, Chandan Rajendra wrote:
> > Checksums are applicable to sectorsize units. The current code uses
> > bio->bv_len units to compute and look up checksums. This works on machines
> > where sectorsize == PAGE_SIZE. This patch makes the checksum computation
> > and look up code to work with sectorsize units.
> >
> > Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
> > Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
> > ---
> >
> > fs/btrfs/file-item.c | 90
> > +++++++++++++++++++++++++++++++++------------------- 1 file changed, 57
> > insertions(+), 33 deletions(-)
> >
> > diff --git a/fs/btrfs/file-item.c b/fs/btrfs/file-item.c
> > index 58ece65..d752051 100644
> > --- a/fs/btrfs/file-item.c
> > +++ b/fs/btrfs/file-item.c
> > @@ -172,6 +172,7 @@ static int __btrfs_lookup_bio_sums(struct btrfs_root
> > *root,>
> > u64 item_start_offset = 0;
> > u64 item_last_offset = 0;
> > u64 disk_bytenr;
> >
> > + u64 page_bytes_left;
> >
> > u32 diff;
> > int nblocks;
> > int bio_index = 0;
> >
> > @@ -220,6 +221,8 @@ static int __btrfs_lookup_bio_sums(struct btrfs_root
> > *root,>
> > disk_bytenr = (u64)bio->bi_iter.bi_sector << 9;
> > if (dio)
> >
> > offset = logical_offset;
> >
> > +
> > + page_bytes_left = bvec->bv_len;
> >
> > while (bio_index < bio->bi_vcnt) {
> >
> > if (!dio)
> >
> > offset = page_offset(bvec->bv_page) + bvec->bv_offset;
> >
> > @@ -243,7 +246,7 @@ static int __btrfs_lookup_bio_sums(struct btrfs_root
> > *root,>
> > if (BTRFS_I(inode)->root->root_key.objectid ==
> >
> > BTRFS_DATA_RELOC_TREE_OBJECTID) {
> >
> > set_extent_bits(io_tree, offset,
> >
> > - offset + bvec->bv_len - 1,
> > + offset + root->sectorsize - 1,
> >
> > EXTENT_NODATASUM, GFP_NOFS);
> >
> > } else {
> >
> > btrfs_info(BTRFS_I(inode)->root-
>fs_info,
> >
> > @@ -281,11 +284,17 @@ static int __btrfs_lookup_bio_sums(struct btrfs_root
> > *root,>
> > found:
> > csum += count * csum_size;
> > nblocks -= count;
> >
> > - bio_index += count;
> > +
> >
> > while (count--) {
> >
> > - disk_bytenr += bvec->bv_len;
> > - offset += bvec->bv_len;
> > - bvec++;
> > + disk_bytenr += root->sectorsize;
> > + offset += root->sectorsize;
> > + page_bytes_left -= root->sectorsize;
> > + if (!page_bytes_left) {
> > + bio_index++;
> > + bvec++;
> > + page_bytes_left = bvec->bv_len;
> > + }
> > +
> >
> > }
> >
> > }
> > btrfs_free_path(path);
> >
> > @@ -432,6 +441,8 @@ int btrfs_csum_one_bio(struct btrfs_root *root, struct
> > inode *inode,>
> > struct bio_vec *bvec = bio->bi_io_vec;
> > int bio_index = 0;
> > int index;
> >
> > + int nr_sectors;
> > + int i;
> >
> > unsigned long total_bytes = 0;
> > unsigned long this_sum_bytes = 0;
> > u64 offset;
> >
> > @@ -459,41 +470,54 @@ int btrfs_csum_one_bio(struct btrfs_root *root,
> > struct inode *inode,>
> > if (!contig)
> >
> > offset = page_offset(bvec->bv_page) + bvec->bv_offset;
> >
> > - if (offset >= ordered->file_offset + ordered->len ||
> > - offset < ordered->file_offset) {
> > - unsigned long bytes_left;
> > - sums->len = this_sum_bytes;
> > - this_sum_bytes = 0;
> > - btrfs_add_ordered_sum(inode, ordered, sums);
> > - btrfs_put_ordered_extent(ordered);
> > + data = kmap_atomic(bvec->bv_page);
>
> I don't think we can have something kmap_atomic()'ed and then do
> allocations under it right? That's why we only kmap_atomic(), do the
> copy, and then unmap, unless I'm forgetting something? Thanks,
>
Josef, you are correct. I will fix it and send out version V3 of the patchset
soon. Thanks for the review.
--
chandan
next prev parent reply other threads:[~2015-08-09 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 7:05 [PATCH V2 00/11] Btrfs: Pre subpagesize-blocksize cleanups Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 01/11] Btrfs: __btrfs_buffered_write: Reserve/release extents aligned to block size Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 02/11] Btrfs: Compute and look up csums based on sectorsized blocks Chandan Rajendra
2015-08-07 18:30 ` Josef Bacik
2015-08-09 11:47 ` Chandan Rajendra [this message]
2015-08-07 7:05 ` [PATCH V2 03/11] Btrfs: Direct I/O read: Work " Chandan Rajendra
2015-08-07 18:46 ` Josef Bacik
2015-08-07 7:05 ` [PATCH V2 04/11] Btrfs: fallocate: Work with " Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 05/11] Btrfs: btrfs_page_mkwrite: Reserve space in sectorsized units Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 06/11] Btrfs: Search for all ordered extents that could span across a page Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 07/11] Btrfs: Use (eb->start, seq) as search key for tree modification log Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 08/11] Btrfs: btrfs_submit_direct_hook: Handle map_length < bio vector length Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 09/11] Btrfs: Limit inline extents to root->sectorsize Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 10/11] Btrfs: Fix block size returned to user space Chandan Rajendra
2015-08-07 7:05 ` [PATCH V2 11/11] Btrfs: Clean pte corresponding to page straddling i_size Chandan Rajendra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1909720.tCRSQLki4e@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=bo.li.liu@oracle.com \
--cc=chandan@mykolab.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox