From: Peter Zijlstra <peterz@infradead.org>
To: Zachary Amsden <zamsden@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
axboe@kernel.dk, hch@infradead.org, akpm@linux-foundation.org,
Paul.Clements@steeleye.com, tytso@mit.edu,
Tejun Heo <tj@kernel.org>, miklos <miklos@szeredi.hu>
Subject: Re: [PATCH] Allow userspace block device implementation
Date: Mon, 27 Jul 2009 14:56:05 +0200 [thread overview]
Message-ID: <1248699365.6987.1628.camel@twins> (raw)
In-Reply-To: <4A6D79F6.3050509@redhat.com>
On Sun, 2009-07-26 at 23:57 -1000, Zachary Amsden wrote:
> Well, it may be a good, bad, idiotic or brilliant idea depending on your
> personal philosophy. I went down this route out of pragmatism.
> Hopefully I have not fully re-invented the wheel.
>
> The patch included allows one to implement a kernel level block device
> in userspace, using an ioctl() based interface to create a sized device
> with given properties, and then receive and respond to bio requests
> issued to the device. One can poll on the associated control socket to
> allow efficient servicing of device requests. So far only strict copy
> to/from user memory is supported, there is no fancy page flipping or
> mapping operations.
Somehow this made me think of FUSE/CUSE... should this be named aBUSE?
Oh wait it is :-), what I'm after is I guess is, can we share some of
the FUSE/CUSE code?
I can only imagine the fun we'll end up with when someone tries swapon
on a user-space block device.. aptly named.
next prev parent reply other threads:[~2009-07-27 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 9:57 [PATCH] Allow userspace block device implementation Zachary Amsden
2009-07-27 12:56 ` Peter Zijlstra [this message]
2009-07-27 13:25 ` Alan Cox
2009-07-27 19:46 ` Zachary Amsden
2009-07-27 20:24 ` Peter Zijlstra
2009-07-27 21:02 ` Alan Cox
2009-07-28 1:21 ` Tejun Heo
2009-07-28 3:53 ` Zachary Amsden
2009-07-28 10:27 ` Alan Cox
2009-07-28 16:00 ` Linus Torvalds
2009-07-28 18:36 ` Kyle Moffett
2009-07-28 18:51 ` Linus Torvalds
2009-07-28 19:07 ` Alan Cox
2009-07-28 19:49 ` Andi Kleen
2009-07-28 20:50 ` Linus Torvalds
2009-07-28 21:09 ` Andi Kleen
2009-07-28 22:56 ` Theodore Tso
2009-08-07 18:08 ` Pavel Machek
2009-08-10 22:47 ` Zachary Amsden
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 20:37 devzero
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=1248699365.6987.1628.camel@twins \
--to=peterz@infradead.org \
--cc=Paul.Clements@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=zamsden@redhat.com \
/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