From: Boaz Harrosh <bharrosh@panasas.com>
To: Jeff Garzik <jeff@garzik.org>,
open-osd mailing-list <osd-dev@open-osd.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCHSET 0/6] exofs: few patches for Linux 2.6.31
Date: Wed, 17 Jun 2009 19:01:55 +0300 [thread overview]
Message-ID: <4A391373.3050301@panasas.com> (raw)
For review the few exofs patches I would like included for current merge window
(Linux 2.6.31)
The main effort on the exofs front was to make it pnfs-exportable. Which for now
only lives in the pnfs tree. So there was not much left outside of that.
Also for final review is the osdblk stacking block driver which is ready
for submission but is missing a supporting user-mode tool, and some more
testing love.
The list of patches:
[PATCH 1/6] exofs: Fix bio leak in error handling path (sync read)
A small and rare bug fix
[PATCH 2/6] exofs: Remove IBM copyrights
As requested by Original author and IBM folks. The code does not belong
to IBM. (Never was)
[PATCH 3/6] exofs: Avoid using file_fsync()
This one is left like this. Since other options suggested are not good
for exofs since it does not have a block-device and any of the BH stuff.
[PATCH 4/6] MAINTAINERS: Add osd maintained files (F:)
Use the new MAINTAINERS F: annotation for the OSD files
[PATCH 5/6] osdblk: a Linux block device for OSD objects
[PATCH 6/6] osdblk: Adjust queue limits to lower device's limits
This is the proposed osdblk driver by Jeff Garzik. It as all the Kernel
pre-requisites, but is missing a user-mode tool and more testing. So I'm
not sure it will make it into this Kernel. But for review.
Thanks
Boaz
next reply other threads:[~2009-06-17 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:01 Boaz Harrosh [this message]
2009-06-17 16:03 ` [PATCH 1/6] exofs: Fix bio leak in error handling path (sync read) Boaz Harrosh
2009-06-17 16:04 ` [PATCH 2/6] exofs: Remove IBM copyrights Boaz Harrosh
2009-06-17 16:05 ` [PATCH 3/6] exofs: Avoid using file_fsync() Boaz Harrosh
2009-06-17 16:06 ` [PATCH 4/6] MAINTAINERS: Add osd maintained files (F:) Boaz Harrosh
2009-06-17 16:07 ` [PATCH 5/6] osdblk: a Linux block device for OSD objects Boaz Harrosh
2009-06-17 16:07 ` [PATCH 6/6] osdblk: Adjust queue limits to lower device's limits Boaz Harrosh
2009-06-18 12:46 ` [osd-dev] [PATCHSET 0/6] exofs: few patches for Linux 2.6.31 Boaz Harrosh
2009-06-18 12:55 ` [PATCH] open-osd: osdblk User Mode utility Boaz Harrosh
2009-06-22 12:15 ` [osd-dev] " Boaz Harrosh
2009-06-18 15:31 ` [osd-dev] [PATCHSET 0/6] exofs: few patches for Linux 2.6.31 Jeff Garzik
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=4A391373.3050301@panasas.com \
--to=bharrosh@panasas.com \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox