From: Chris Mason <chris.mason@oracle.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Arne Jansen <sensille@gmx.net>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] scrub updates for 3.1
Date: Tue, 5 Jul 2011 18:52:48 -0700 (PDT) [thread overview]
Message-ID: <1309917127-sup-8901@shiny> (raw)
In-Reply-To: <4E13B4FA.8050008@cn.fujitsu.com>
Excerpts from Li Zefan's message of 2011-07-05 21:06:02 -0400:
> 21:00, Arne Jansen worte:
> > Hi Chris,
> >
> > since rc-6 seems to be the last rc for 3.0 and in case you're already
> > preparing your pull request for 3.1, can you please pull the following
> > updates for scrub, based on your for-linus tree (2f7e33d432)?
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/arne/btrfs-unstable-arne.git
> > for-chris
> >
> > It just contains the readahead patch, which gives a significant
> > performance improvement for scrub. Currently scrub is the only
> > consumer.
> >
> > Thanks,
> > Arne
> >
> > Arne Jansen (7):
> > btrfs: add an extra wait mode to read_extent_buffer_pages
> > btrfs: add READAHEAD extent buffer flag
> > btrfs: state information for readahead
> > btrfs: initial readahead code and prototypes
> > btrfs: hooks for readahead
> > btrfs: test ioctl for readahead
>
> Do we really want this ioctl that is merely for testing some kernel
> APIs in our upstream kernel?
I'd like to avoid the ioctl for now, since once it is there we're stuck
with it forever. At least for the 3.1 pull lets keep it out please.
-chris
next prev parent reply other threads:[~2011-07-06 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 13:00 [GIT PULL] scrub updates for 3.1 Arne Jansen
2011-07-06 1:06 ` Li Zefan
2011-07-06 1:52 ` Chris Mason [this message]
2011-07-06 6:04 ` Arne Jansen
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=1309917127-sup-8901@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=sensille@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).