From: Boaz Harrosh <bharrosh@panasas.com>
To: open-osd <osd-dev@open-osd.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCHSET 0/7] exofs: Some pending changes for 2.6.39
Date: Tue, 08 Feb 2011 18:15:24 +0200 [thread overview]
Message-ID: <4D516C1C.8060504@panasas.com> (raw)
Submitted for review a few patches for the next Merge window.
List of patches:
[PATCH 1/7] exofs: Trivial: fix some indentation and debug prints
[PATCH 2/7] exofs: Optimize read_4_write
[PATCH 3/7] exofs: simple fsync race fix
Nick please re-review your patch. I think it is needed.
I ran with it for a while now. It makes perfect sense.
[PATCH 4/7] exofs: Override read-ahead to align on stripe_size
Thanks to Chris Mason and Marc Dionne. This patch is a nice
bonus for the kind of striping done in exofs.
[PATCH 5/7] exofs: Add option to mount by osdname
A long over do on this simple option
[PATCH 6/7] exofs: Write sbi->s_nextid as part of the Create command
[PATCH 7/7] exofs: deprecate the commands pending counter
Thanks
Boaz
next reply other threads:[~2011-02-08 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 16:15 Boaz Harrosh [this message]
2011-02-08 16:17 ` [PATCH 1/7] exofs: trivial: fix some indentation and debug prints Boaz Harrosh
2011-02-08 16:26 ` [PATCH 2/7] exofs: Optimize read_4_write Boaz Harrosh
2011-02-08 16:29 ` [PATCH 3/7] exofs: simple fsync race fix Boaz Harrosh
2011-02-08 16:31 ` [PATCH 4/7] exofs: Override read-ahead to align on stripe_size Boaz Harrosh
2011-02-08 16:35 ` [PATCH 5/7] exofs: Add option to mount by osdname Boaz Harrosh
2011-02-08 16:40 ` [PATCH 6/7] exofs: Write sbi->s_nextid as part of the Create command Boaz Harrosh
2011-02-08 16:42 ` [PATCH 7/7] exofs: deprecate the commands pending counter Boaz Harrosh
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=4D516C1C.8060504@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=osd-dev@open-osd.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 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.