All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Dan Smith <danms@us.ibm.com>, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Add dm-userspace to the Xen kernel
Date: Thu, 15 Jun 2006 16:44:37 -0500	[thread overview]
Message-ID: <4491D4C5.6020308@us.ibm.com> (raw)
In-Reply-To: <4491D346.5070909@us.ibm.com>

Nivedita Singhvi wrote:
> Anthony Liguori wrote:
>> I think dm-userspace is great, but I don't think it belongs in 
>> patches/.  To quote Chris W.:
>>
>> "Good things there are bits that are ready to go upstream or fixes to 
>> base Linux that are transient by version (backport of a fix that's in 
>> the -rc for the next kernel or somesuch)."
>>
>> Until this ends up in -mm, I really don't think we should add this to 
>> the -xen tree as it has no dependence on Xen.  We should be good 
>> members of the kernel community here and go through the normal 
>> channels.  At any rate, I would think that you would want it to be 
>> useful first before adding it which means bringing in all of the 
>> tools into the tree.
>
> It won't be useful in the kernel unless there are actual
> consumers, of which Xen could/might be one. Having a use
> case flesh out problems and get the performance and design
> architecture examined in detail will be useful to the Linux
> maintainers - they get something more robust and better
> designed, although it's certainly not Xen's obligation to
> provide that, per se. I'm just seeing the possibility of
> mutual benefit, here.
>
> That said, I believe since the patch is in the device-mapper
> tree for review, there is a good chance it will go into
> kernel in any case.

Agreed.  I think it's a good idea to let it go through that review 
process before going into the Xen tree.  As I said, once it's in -mm, I 
would imagine that it the interfaces would be stable enough that there's 
no harm putting it into the Xen tree.

Especially since libdmu is being considered for inclusion in the 
device-mapper userspace.  Things would get pretty ugly if the 
dm-userspace ABI changes between now and when it shows up in -mm as 
there'd be conflicting userspace packages.

Regards,

Anthony Liguori

> thanks,
> Nivedita
>

  reply	other threads:[~2006-06-15 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 21:07 [PATCH] Add dm-userspace to the Xen kernel Anthony Liguori
2006-06-15 21:38 ` Nivedita Singhvi
2006-06-15 21:44   ` Anthony Liguori [this message]
2006-06-15 22:09     ` Dan Smith
  -- strict thread matches above, loose matches on Subject: below --
2006-06-15 19:47 Dan Smith
2006-06-16 18:31 ` Niraj Tolia
2006-06-16 18:50   ` Dan Smith
2006-06-16 18:56   ` Anthony Liguori
2006-06-16 19:39     ` Andrew Warfield
2006-06-16 19:41     ` Niraj Tolia
2006-06-09 21:08 Dan Smith
2006-06-09 21:48 ` Anthony Liguori
2006-06-09 23:12   ` Dan Smith
2006-06-10  8:55     ` Keir Fraser
2006-06-10 20:40 ` Bastian Blank
2006-06-12 14:52   ` Dan Smith
2006-06-13  8:57     ` Bastian Blank

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=4491D4C5.6020308@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=danms@us.ibm.com \
    --cc=niv@us.ibm.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.