[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090104153841.GA16569@infradead.org>
Date: Sun, 4 Jan 2009 10:38:41 -0500
From: Christoph Hellwig <hch@...radead.org>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
Matthew Wilcox <matthew@....cx>,
Benny Halevy <bhalevy@...asas.com>,
Jeff Garzik <jeff@...zik.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...IV.linux.org.uk>,
Avishay Traeger <avishay@...il.com>,
open-osd development <osd-dev@...n-osd.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 7/9] exofs: mkexofs
On Sun, Jan 04, 2009 at 05:20:42PM +0200, Boaz Harrosh wrote:
>
> User-mode Interface is another matter. There are some ideas and some already
> implemented.
> [Hosted on open-osd.org
> see: http://git.open-osd.org/gitweb.cgi?p=osc-osd/.git;a=summary
> look inside the osd-initiator directory]
> And I have a toy interface that adds no new entries into the Kernel in
> the form of an OSDVFS module, that will let you access the raw OSD device
> through the VFS name-space.
>
> The lack of any user-mode API is just the lack of any current need/priority,
> or that I'm the only one working on OSD. But nothing that could not be solved
> in two weeks of pragmatic work. Surly it's not a paradigm problem.
For mkfs/repair direct use by databases, etc you want a userspace
library, too. The easiest way to get started would to simply take the
kernel libosd and make it work ontop of SG_IO.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists