From: Boaz Harrosh <bharrosh@panasas.com>
To: Greg KH <greg@kroah.com>
Cc: Benny Halevy <bhalevy@panasas.com>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
kernel-janitors@vger.kernel.org, linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [ANNOUNCE] linux-staging tree created
Date: Wed, 11 Jun 2008 20:43:48 +0300 [thread overview]
Message-ID: <48500ED4.3010808@panasas.com> (raw)
In-Reply-To: <20080611162534.GD22134@kroah.com>
Greg KH wrote:
> On Wed, Jun 11, 2008 at 12:50:34PM +0300, Boaz Harrosh wrote:
>> Benny Halevy wrote:
>>> Greg,
>>>
>>> The OSD initiator (see
>>> http://git.open-osd.org/gitweb.cgi?p=open-osd.git;a=summary)
>>> looks in principle like a great fit for linux-staging.
>>>
>> The patches are not yet there, Benny. They are currently
>> out-of-tree here:
>> http://git.open-osd.org/gitweb.cgi?p=osd-lib.git;a=summary
>>
>> It will take me until end of next week to separate them into
>> a consumable patchset. Which will also move them in-tree.
>>
>>> What would be the mechanics of including it?
>>>
>> I want to send them to linux-scsi-ml and also To: Greg KH
>> Requesting to be included in "linux-staging tree". Is that
>> sufficient?
>
> If they are to go into linux-scsi, why would you need/want them in the
> -staging tree as well?
>
We're jumping the guns here a bit, but ...
The code is pretty stable and robust as far as the protocol and performance
is concerned, surly once I in-tree them, divide them into patches, prettify
comments, add file-headers, and checkpatch them.
But the bigger implications are not yet clear, and will need advise from
the list, which could take time. Mainly in regard to upper ULD and tests.
Currently there are 4 users for this code:
- pNFS-over-objects layout driver
- pNFS-over-objects Simple Server implementation (spNFS)
- OSDVFS - Virtual psuedo file system to access and debug OSD luns from user mode.
(This is not the OSDFS from IBM which is a general FS over objects,
but a direct representation of the OSD Lun to user mode)
- Testing
The first 3 are their own ULD and do not need a proper SCSI-ULD. With some
changes to sg.c they can manage with what we have now. The later is just
for debugging.
On the other hand a true OSD-ULD that exports /dev/osdx char and/or block
devices, has merits and future directions of it's own. And will eliminate
the need for changes in sg.c
So the mechanics are pretty much there but the direction is not clear, which
will govern the folders/exports/dependencies. But I'm not sure -staging tree
will help in any of that. I do have my git.open-osd.org exports and can manage
all that there. It could help in exposure and testing of the code.
> thanks,
>
> greg k-h
Thanks
Boaz
next prev parent reply other threads:[~2008-06-11 17:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:05 [ANNOUNCE] linux-staging tree created Greg KH
2008-06-10 19:06 ` linux-staging status for June 10, 2008 Greg KH
2008-06-10 22:52 ` [ANNOUNCE] linux-staging tree created Theodore Tso
2008-06-10 23:05 ` Greg KH
2008-06-11 0:07 ` Felipe Balbi
2008-06-11 3:28 ` Greg KH
2008-06-11 1:05 ` Nigel Cunningham
2008-06-11 3:29 ` Greg KH
2008-06-11 4:00 ` Nigel Cunningham
2008-06-11 16:24 ` Greg KH
2008-06-11 4:03 ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree created) Nigel Cunningham
2008-06-11 16:23 ` Greg KH
2008-06-11 9:27 ` [ANNOUNCE] linux-staging tree created Benny Halevy
2008-06-11 9:50 ` Boaz Harrosh
2008-06-11 9:58 ` Felipe Balbi
2008-06-11 16:25 ` Greg KH
2008-06-11 17:43 ` Boaz Harrosh [this message]
2008-06-11 16:25 ` Greg KH
2008-06-11 10:45 ` Will Newton
2008-06-11 16:26 ` Greg KH
2008-06-12 11:37 ` Will Newton
2008-06-12 23:54 ` Greg KH
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:33 ` John W. Linville
2008-06-13 15:51 ` Luis R. Rodriguez
[not found] ` <20080613143328.GA16506-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-14 0:28 ` Greg KH
[not found] ` <43e72e890806130714k535b041evaf750209ea492c47-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14 0:27 ` Greg KH
2008-06-17 12:51 ` Pavel Machek
2008-07-02 23:11 ` Greg KH
2008-07-14 2:50 ` Jike Song
2008-07-14 2:56 ` Greg KH
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=48500ED4.3010808@panasas.com \
--to=bharrosh@panasas.com \
--cc=bhalevy@panasas.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).