From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Zachary Amsden <zamsden@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
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,
miklos <miklos@szeredi.hu>
Subject: Re: [PATCH] Allow userspace block device implementation
Date: Tue, 28 Jul 2009 11:27:34 +0100 [thread overview]
Message-ID: <20090728112734.5a75752d@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4A6E764E.80805@redhat.com>
> BTW, implementing something like this via FUSE would be extremely
> unpleasant. I'd need another layer on top, probably via the loop
> device, to get to the actual partitions of the block devices.
Use device mapper. Really we should shoot all the partition code in the
kernel but the back compatibility is a bit tricky. We don't actually need
the partition code any more.
next prev parent reply other threads:[~2009-07-28 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 9:57 Zachary Amsden
2009-07-27 12:56 ` Peter Zijlstra
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 [this message]
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
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=20090728112734.5a75752d@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®