public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC] btrfs: allow extent buffer helpers to skip cross-page handling
Date: Thu, 23 Nov 2023 19:50:32 +0100	[thread overview]
Message-ID: <20231123185032.GA31451@twin.jikos.cz> (raw)
In-Reply-To: <c1c0dacb-8db5-4b6b-90f1-a71487fb44dd@gmx.com>

On Thu, Nov 23, 2023 at 06:31:41AM +1030, Qu Wenruo wrote:
> 
> 
> On 2023/11/23 00:16, David Sterba wrote:
> > On Thu, Nov 16, 2023 at 03:49:06PM +1030, Qu Wenruo wrote:
> >> --- a/fs/btrfs/disk-io.c
> >> +++ b/fs/btrfs/disk-io.c
> >> @@ -80,8 +80,16 @@ static void csum_tree_block(struct extent_buffer *buf, u8 *result)
> >>   	char *kaddr;
> >>   	int i;
> >>
> >> +	memset(result, 0, BTRFS_CSUM_SIZE);
> >>   	shash->tfm = fs_info->csum_shash;
> >>   	crypto_shash_init(shash);
> >> +
> >> +	if (buf->addr) {
> >> +		crypto_shash_digest(shash, buf->addr + offset_in_page(buf->start) + BTRFS_CSUM_SIZE,
> >> +				    buf->len - BTRFS_CSUM_SIZE, result);
> >> +		return;
> >> +	}
> >
> > This duplicates the address and size
> >> +
> >>   	kaddr = page_address(buf->pages[0]) + offset_in_page(buf->start);
> >>   	crypto_shash_update(shash, kaddr + BTRFS_CSUM_SIZE,
> >>   			    first_page_part - BTRFS_CSUM_SIZE);
> >> @@ -90,7 +98,6 @@ static void csum_tree_block(struct extent_buffer *buf, u8 *result)
> >>   		kaddr = page_address(buf->pages[i]);
> >>   		crypto_shash_update(shash, kaddr, PAGE_SIZE);
> >>   	}
> >> -	memset(result, 0, BTRFS_CSUM_SIZE);
> >>   	crypto_shash_final(shash, result);
> >
> > I'd like to have only one code doing the crypto_shash_ calls, so I'm
> > suggesting this as the final code (the diff is not clear);
> 
> This looks good to me, mind to update it inside your branch?

There's something wrong with my updates, it fails in the first test so
I've verified your works and the used it in misc-next for now.

  parent reply	other threads:[~2023-11-23 18:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  5:19 [PATCH RFC] btrfs: allow extent buffer helpers to skip cross-page handling Qu Wenruo
2023-11-20 17:00 ` David Sterba
2023-11-20 20:25   ` Qu Wenruo
2023-11-21 15:35     ` David Sterba
2023-11-21 20:37       ` Qu Wenruo
2023-11-21 21:14         ` David Sterba
2023-11-21 21:30           ` Qu Wenruo
2023-11-22 13:23             ` David Sterba
2023-11-22 13:34 ` David Sterba
2023-11-22 13:46 ` David Sterba
2023-11-22 20:01   ` Qu Wenruo
2023-11-22 22:05     ` David Sterba
2023-11-23 18:50     ` David Sterba [this message]
2023-11-23 20:51     ` Qu Wenruo
2023-11-24 16:03       ` David Sterba

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=20231123185032.GA31451@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.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