> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Tuesday, February 09, 2010 2:30 AM
> To: Jan Beulich; Dan Magenheimer
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: tmem - really default to on?
>
> On 09/02/2010 09:25, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>
> >> Oops, I see in re-reading your earlier posts that you
> >> are enabling it by default for domU as well. In that
> >> case I agree, sadly, that your best choice might be to
> >> disable tmem completely in your Xen hypervisor, at least
> >> until the Xen fragmentation issues are resolved.
> >
> > And why would that not hold for the upstream version? That's what
> > the mail thread was about - whether for 4.0 defaulting tmem to on
> > should be reverted. I hence take your above statement as a 'yes'
> > to that question. Keir, will you do this then, or should I submit a
> > revert patch?
>
> Yes, I can do it. It's a shame though.
>
> -- Keir
Yes, I agree as long as we are just flipping the default to off.
Turning tmem on by default served its purpose of shaking out other
problems, but unfortunately too late in the 4.0 release cycle to
fix them all in time for the 4.0 release.
Keir, please revert 20655/20758. Ideally, I'd like to
see the default flipped back to ON in xen-unstable immediately
after 4.0 is split off.
(And, for the record, tmem is still IN the 4.0 release,
it just needs to be explicitly enabled to use it and
has some known bugs.)
Dan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home