From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: Goldwyn Rodrigues <rgoldwyn@suse.de>,
linux-btrfs@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>,
David Sterba <dsterba@suse.com>
Subject: Re: [RFC] Converging userspace and kernel code
Date: Mon, 9 Jan 2017 01:31:48 -0800 [thread overview]
Message-ID: <20170109093148.GA7341@infradead.org> (raw)
In-Reply-To: <65341974-d15f-408c-abad-98c2a5bb8743@cn.fujitsu.com>
On Mon, Jan 09, 2017 at 10:11:29AM +0800, Qu Wenruo wrote:
> (I'm already trying to re-implement btrfs_map_block() in btrfs-progs with a
> better interface in out-of-tree offline scrub patchset)
How about doing the right thing in the kernel as well? While looking
at the btrfs abuse of the block REQ_* flag I had to read and understand
__btrfs_map_block and agree it's ripe for refactoring.
next prev parent reply other threads:[~2017-01-09 9:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 13:16 [RFC] Converging userspace and kernel code Goldwyn Rodrigues
2017-01-09 2:11 ` Qu Wenruo
2017-01-09 9:31 ` Christoph Hellwig [this message]
2017-01-09 12:06 ` Goldwyn Rodrigues
2017-01-10 0:35 ` Qu Wenruo
2017-01-10 0:56 ` Omar Sandoval
2017-01-09 15:31 ` Eric Sandeen
2017-01-09 21:34 ` Omar Sandoval
2017-01-09 21:38 ` Jeff Mahoney
2017-01-10 1:46 ` Darrick J. Wong
2017-01-10 2:24 ` Qu Wenruo
2017-01-10 3:28 ` Anand Jain
2017-01-10 12:14 ` Goldwyn Rodrigues
2017-01-10 15:20 ` Anand Jain
2017-01-10 16:04 ` Goldwyn Rodrigues
2017-01-11 2:23 ` Anand Jain
2017-01-11 2:32 ` Qu Wenruo
2017-01-11 2:55 ` Goldwyn Rodrigues
2017-01-11 10:58 ` Anand Jain
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=20170109093148.GA7341@infradead.org \
--to=hch@infradead.org \
--cc=dsterba@suse.com \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=rgoldwyn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.