xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com,
	Konrad Wilk <konrad.wilk@oracle.com>,
	Vasiliy G Tolstov <v.tolstov@selfip.ru>,
	JBeulich@novell.com, Dushmanta Mohapatra <dmpatra@gmail.com>
Subject: RE: [PATCH] [linux-2.6.39.x for xen] tmem: self-ballooning and frontswap-selfshrinking
Date: Tue, 7 Jun 2011 09:59:03 -0700 (PDT)	[thread overview]
Message-ID: <dfc9d187-fa21-45fc-86e4-db607e5bd401@default> (raw)
In-Reply-To: <1307464812.775.665.camel@zakaz.uk.xensource.com>

> From: Ian Campbell [mailto:Ian.Campbell@eu.citrix.com]
> >
> > Although you're right, as I am fresh off a 2-1/2 year odyssey of
> > upstreaming cleancache, AND since this is almost certainly Xen
> > specific AND since there will likely be some changes over time
> > which could conceivably make this unnecessary, I would be content
> > with carrying this in a Xen-only tree for the foreseeable future.
> 
> As someone who is fresh of a 5+ year odyssey of upstreaming a Xen-only
> tree into mainline I must strongly object to this approach.
> 
> We have had a long uphill battle to get ourselves to the state we are in
> today and the approach you are suggesting is absolutely counter to the
> philosophy we have built up whilst doing that and accepting this undoes
> all of the good work up until now.
> 
> Getting stuff into a Xen tree is not an aim in and of itself but merely
> a conduit towards upstream. Nothing should be going into the Xen stable
> trees with the explicit aim of staying there for the foreseeable future.
> 
> If you want to run a tmem-only tree with stuff you don't intend to send
> upstream yet in it then that is your prerogative, please don't ask the
> rest of us to carry that burden.

Well that's a bit harsh.  Perhaps I should clarify: By "for the
foreseeable future", I meant I don't expect it to be a candidate
for 3.1 or probably even 3.2.  I didn't mean to imply that
I wasn't going to try, just that I wasn't going to try for 3.1.

I see Konrad's tree as kind of a linux-next specific to Xen where
Xen-ish functionality/fixes can be exposed "officially" to Xen users
before the upstreaming battle is fought.  I've had many requests
for tmem over the last couple of years but haven't had a good
foundation for delivery.  Are you saying nothing should go in
Konrad's tree unless it is immediately upstreamable?

Related, there's a really good article* in lwn.net of James Bottomley's
talk about the Android fork (subscribers only as of now) that
I think nicely summarizes our frustration with upstreaming battles.

Dan

* http://lwn.net/Articles/446297/ ... This may not be public for
a week or two.

  reply	other threads:[~2011-06-07 16:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 22:12 [PATCH] [linux-2.6.39.x for xen] tmem: self-ballooning and frontswap-selfshrinking Dan Magenheimer
2011-06-07  9:34 ` Ian Campbell
2011-06-07 14:37   ` Vasiliy G Tolstov
2011-06-07 16:40     ` Dan Magenheimer
2011-06-07 16:21   ` Dan Magenheimer
2011-06-07 16:40     ` Ian Campbell
2011-06-07 16:59       ` Dan Magenheimer [this message]
2011-06-07 19:37         ` Ian Campbell
2011-06-07 16:46     ` Ian Campbell
2011-06-09 17:21 ` Daniel Kiper
2011-06-09 21:12   ` Dan Magenheimer
2011-06-10 11:53     ` Daniel Kiper
2011-06-14  9:15   ` Ian Campbell

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=dfc9d187-fa21-45fc-86e4-db607e5bd401@default \
    --to=dan.magenheimer@oracle.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=dmpatra@gmail.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=v.tolstov@selfip.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).