From: Christoph Hellwig <hch@infradead.org>
To: David Sterba <dsterba@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: don't offload CRCs generation to helpers if it is fast
Date: Mon, 10 Apr 2023 10:17:49 -0700 [thread overview]
Message-ID: <ZDREvSPL3ePYAx4X@infradead.org> (raw)
In-Reply-To: <ZC5XPqC9+us0sLPX@infradead.org>
On Wed, Apr 05, 2023 at 10:23:10PM -0700, Christoph Hellwig wrote:
> On Thu, Apr 06, 2023 at 01:14:55AM +0200, David Sterba wrote:
> > > This series implements that and also tidies up various lose ends around
> > > that.
> >
> > I've picked patch 1 as it's a standalone fix and should go to stable
> > trees, the rest is in for-next and still queued for 6.4.
>
> So the usual question:
>
> - should I resend the series with a commit log that you're prefer?
> - or just deliver a new commit log?
> - or are you just going to fix it up?
Dave, can you help me on how you want me to proceed here?
next prev parent reply other threads:[~2023-04-10 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 0:13 don't offload CRCs generation to helpers if it is fast Christoph Hellwig
2023-03-29 0:13 ` [PATCH 1/4] btrfs: fix fast csum detection Christoph Hellwig
2023-04-03 18:35 ` David Sterba
2023-04-04 5:06 ` Christoph Hellwig
2023-04-04 17:13 ` David Sterba
2023-03-29 0:13 ` [PATCH 2/4] btrfs: remove the sync_writers field in struct btrfs_inode Christoph Hellwig
2023-04-05 13:50 ` David Sterba
2023-03-29 0:13 ` [PATCH 3/4] btrfs: never defer I/O submission for fast CRC implementations Christoph Hellwig
2023-03-29 0:13 ` [PATCH 4/4] btrfs: remove hipri_workers workqueue Christoph Hellwig
2023-03-30 15:42 ` don't offload CRCs generation to helpers if it is fast Chris Mason
2023-03-30 21:06 ` Christoph Hellwig
2023-03-31 17:31 ` David Sterba
2023-04-05 23:14 ` David Sterba
2023-04-06 5:23 ` Christoph Hellwig
2023-04-10 17:17 ` Christoph Hellwig [this message]
2023-04-11 19:09 ` 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=ZDREvSPL3ePYAx4X@infradead.org \
--to=hch@infradead.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
/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