From: Jeff Garzik <jeff@garzik.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: open-osd mailing-list <osd-dev@open-osd.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [osd-dev] [PATCHSET 0/6] exofs: few patches for Linux 2.6.31
Date: Thu, 18 Jun 2009 11:31:28 -0400 [thread overview]
Message-ID: <4A3A5DD0.6060805@garzik.org> (raw)
In-Reply-To: <4A3A370D.10704@panasas.com>
Boaz Harrosh wrote:
> On 06/17/2009 07:01 PM, Boaz Harrosh wrote:
>> [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.
>>
>
> Jeff hi.
>
> I've hacked up a very quick and dirty small utility for Creating / Removing / Resizing
> objects on an OSD device. [I'm sending as reply to this mail]
Looks good to me!
> Please give it a fast testing. Should we now submit the osdblk driver, for 2.6.31?
> Which tree? I can push it through the open-osd.org tree. The driver was included for
> some weeks in linux-next through that tree.
I'll try to give it a test early next week, as my OSD simulator setup is
completely disassembled at the moment.
Yes, please go ahead and push the driver. In general, Linus accepts new
drivers to the kernel at any time, even during a -rc, once the pre-reqs
are upstream.
Jeff
prev parent reply other threads:[~2009-06-18 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:01 [PATCHSET 0/6] exofs: few patches for Linux 2.6.31 Boaz Harrosh
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 ` Jeff Garzik [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=4A3A5DD0.6060805@garzik.org \
--to=jeff@garzik.org \
--cc=bharrosh@panasas.com \
--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