All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Jansen <sensille@gmx.net>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Chris Mason <chris.mason@oracle.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] scrub updates for 3.1
Date: Wed, 06 Jul 2011 08:04:24 +0200	[thread overview]
Message-ID: <4E13FAE8.4000303@gmx.net> (raw)
In-Reply-To: <4E13B4FA.8050008@cn.fujitsu.com>

On 06.07.2011 03:06, Li Zefan wrote:
> 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?

Oh, I completely forgot about that. You're right of course. I pushed
the for-chris branch again, it now looks like this:

Arne Jansen (6):
      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: use readahead API for scrub

 fs/btrfs/Makefile    |    3 +-
 fs/btrfs/ctree.h     |   21 ++
 fs/btrfs/disk-io.c   |   85 +++++-
 fs/btrfs/disk-io.h   |    2 +
 fs/btrfs/extent_io.c |    9 +-
 fs/btrfs/extent_io.h |    4 +
 fs/btrfs/reada.c     |  949
++++++++++++++++++++++++++++++++++++++++++++++++++
 fs/btrfs/scrub.c     |  116 +++----
 fs/btrfs/volumes.c   |    8 +
 fs/btrfs/volumes.h   |    8 +
 10 files changed, 1133 insertions(+), 72 deletions(-)
 create mode 100644 fs/btrfs/reada.c

Thanks,
Arne

      parent reply	other threads:[~2011-07-06  6:04 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
2011-07-06  6:04   ` Arne Jansen [this message]

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=4E13FAE8.4000303@gmx.net \
    --to=sensille@gmx.net \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lizf@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 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.