public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo-sources and xen blktap driver?
Date: Sat, 7 Jan 2012 19:43:03 -0500	[thread overview]
Message-ID: <CA+czFiBpyN5-ZZNuVgg0Gd4Cp5QWyLL=isWL_RVJdvE5Ygsq9g@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGXvDos92u_+8Oj70QKD+4EFT8Szfi4Vy95sQfbp7B=udA@mail.gmail.com>

On Sat, Jan 7, 2012 at 7:36 PM, Pandu Poluan <pandu@poluan.info> wrote:
> On Jan 8, 2012 12:43 AM, "Michael Mol" <mikemol@gmail.com> wrote:
>> On Sat, Jan 7, 2012 at 11:35 AM, Pandu Poluan <pandu@poluan.info> wrote:
>> > On Jan 7, 2012 8:44 PM, "victor romanchuk" <rom@persimplex.net> wrote:
>> >>
>> >> Konstantinos Agouros wrote, at 01/07/2012 03:51 PM:
>> >> > since xen got into the mainstream kernel the way to go is to use
>> >> > gentoo-sources for dom0 and the domUs. However the blktap modules are
>> >> > not
>> >> > there. Is there any way to get this to work?
>> >>
>> >> blktap drivers were excluded from kernel mainline since 3.x, these two
>> >> threads
>> >> from xen-users mailing list might put some light in that context:
>> >>
>> >>
>> >>
>> >> http://old-list-archives.xen.org/archives/html/xen-users/2011-07/msg00637.html
>> >>
>> >>
>> >> http://old-list-archives.xen.org/archives/html/xen-users/2011-10/msg00065.html
>> >>
>> >> the latest sys-kernel/xen-sources containing working blktap (not
>> >> blktap2)
>> >> is
>> >> 2.6.38 (this is buggy from my point of view; i'm still sitting on
>> >> 2.6.34-r5 for
>> >> production installations)
>> >>
>> >
>> > Can someone shed a light on the importance of blktap, i.e., why one
>> > would
>> > want to use it when -- as someone explained in the first email thread
>> > you
>> > gave -- blkfront+blkend is enough for paravirtualization?
>>
>> Reading through the linked threads, it sounds like the benefit stems
>> from being able to shim things in between the front and back ends.
>>
>> You might want that for any number of reasons:
>> * a block encryption layer
>> * a metering layer
>> * a read/write masking layer
>> * an intercept to have the block device exist on (or be mirrored to)
>> on another system.
>>
>> etc.
>>
>
> Ah yes, of course.
>
> One of the threads also mentioned that blktap might be better implemented in
> userspace.

Well, there's that, too. For a while, there's been a long push in
Linux to get anything that could remotely reasonably be done in
userspace out of kernelspace.

-- 
:wq



      reply	other threads:[~2012-01-08  0:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 11:51 [gentoo-user] gentoo-sources and xen blktap driver? Konstantinos Agouros
2012-01-07 13:41 ` victor romanchuk
2012-01-07 16:35   ` Pandu Poluan
2012-01-07 17:40     ` Michael Mol
2012-01-08  0:36       ` Pandu Poluan
2012-01-08  0:43         ` Michael Mol [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='CA+czFiBpyN5-ZZNuVgg0Gd4Cp5QWyLL=isWL_RVJdvE5Ygsq9g@mail.gmail.com' \
    --to=mikemol@gmail.com \
    --cc=gentoo-user@lists.gentoo.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