linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: linux-ext4@vger.kernel.org
Cc: adilger@whamcloud.com, colyli@gmail.com
Subject: [PATCH 0/3] directory index patch set v2
Date: Mon, 20 Jun 2011 22:28:44 +0200	[thread overview]
Message-ID: <20110620202631.2473133.4166.stgit@localhost.localdomain> (raw)

The following series implements...

      ext4: Fix compilation with -DDX_DEBUG v2
      ext4 directory index: read-ahead blocks v2
      dx read-ahead: Map blocks with a single semaphore lock

TODO: 
- Fix compilatation of ext3 with -DDX_DEBUG.
- Use worker threads for read-aheads?


 Documentation/filesystems/ext4.txt |    6 ++
 fs/ext4/ext4.h                     |    3 +
 fs/ext4/inode.c                    |   95 ++++++++++++++++++++++++++++++++++++
 fs/ext4/namei.c                    |   84 ++++++++++++++++++++++++++++++--
 fs/ext4/super.c                    |   17 ++++++
 5 files changed, 199 insertions(+), 6 deletions(-)


             reply	other threads:[~2011-06-20 20:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 20:28 Bernd Schubert [this message]
2011-06-20 20:28 ` [PATCH 1/3] ext4: Fix compilation with -DDX_DEBUG v2 Bernd Schubert
     [not found]   ` <4E0012A4.1010608@gmail.com>
2011-06-21 15:26     ` Bernd Schubert
2011-07-16 23:41   ` Ted Ts'o
2011-07-19 15:02     ` Bernd Schubert
2011-07-20 21:25       ` Jan Kara
2011-06-20 20:28 ` [PATCH 2/3] ext4 directory index: read-ahead blocks v2 Bernd Schubert
2011-07-16 23:59   ` Ted Ts'o
2011-07-17  1:02     ` Bernd Schubert
2011-07-17 13:12       ` Theodore Tso
2011-07-18  0:23         ` Ted Ts'o
2011-07-19 14:22           ` Bernd Schubert
2011-06-20 20:29 ` [PATCH 3/3] dx read-ahead: Map blocks with a single semaphore lock Bernd Schubert

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=20110620202631.2473133.4166.stgit@localhost.localdomain \
    --to=bernd.schubert@itwm.fraunhofer.de \
    --cc=adilger@whamcloud.com \
    --cc=colyli@gmail.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).