From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: tmem - really default to on?
Date: Tue, 09 Feb 2010 09:25:29 +0000 [thread overview]
Message-ID: <4B713819020000780002E682@vpn.id2.novell.com> (raw)
In-Reply-To: <40177025-a986-49bb-9383-4175212d6e5f@default>
>>> Dan Magenheimer <dan.magenheimer@oracle.com> 08.02.10 19:30 >>>
>> > of tmem on a per-domain basis. Then I can't see why it should be
>> > only our Dom0 to be affected. And finally I can't see how the same
>> > couldn't happen when only DomU-s use tmem.
>>
>> I'm suggesting disabling CONFIG_TMEM for default dom0 compile
>
>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?
Jan
next prev parent reply other threads:[~2010-02-09 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 9:41 tmem - really default to on? Jan Beulich
[not found] ` <8ce008cd-3942-4a25-9c09-1d099e2c04fb@default>
2010-02-01 8:16 ` Jan Beulich
2010-02-04 21:01 ` Dan Magenheimer
2010-02-05 8:39 ` Jan Beulich
2010-02-05 18:44 ` Dan Magenheimer
2010-02-08 8:33 ` Jan Beulich
2010-02-08 17:18 ` Dan Magenheimer
2010-02-08 18:30 ` Dan Magenheimer
2010-02-09 9:25 ` Jan Beulich [this message]
2010-02-09 9:30 ` Keir Fraser
2010-02-09 15:43 ` Dan Magenheimer
2010-02-09 9:10 ` Jan Beulich
2010-02-09 10:45 ` Tim Deegan
2010-02-09 13:00 ` Jan Beulich
2010-02-09 13:31 ` Keir Fraser
2010-02-09 13:59 ` Tim Deegan
2010-02-09 16:07 ` Dan Magenheimer
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=4B713819020000780002E682@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.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 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).