From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Satoshi Uchida <s-uchida@ap.jp.nec.com>,
xen-devel@lists.xensource.com,
John Levon <levon@movementarian.org>
Subject: Re: [PATCH] Sysfs Interface for balloon driver
Date: Wed, 20 Sep 2006 18:40:15 -0500 [thread overview]
Message-ID: <4511D15F.90904@us.ibm.com> (raw)
In-Reply-To: <3AAA99889D105740BE010EB6D5A5A3B202A2AC@paddington.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> Personally, I think the ballooning information ought to be exposed as
>>
> a
>
>> module parameter and appear in the sysfs module path. I've always
>> thought /sys/hypervisor ought to expose information from the
>>
> hypervisor.
>
> I don't think the memory target stuff is a driver. 'balloon' should not
> appear in the name anyhow -- this stuff is getting ever more closely
> integrated with Linux's core memory management anyhow, it's definitely
> not a driver.
>
> I sort of slightly buy Anthony's argument that /sys/hypervisor should
> just expose information about the hypervisor.
>
> /sys/devices/system/memory/{target,current,max,..} ?
>
Works for me.
Regards,
Anthony Liguori
> Ian
>
>
>
>
next prev parent reply other threads:[~2006-09-20 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 0:26 [PATCH] Sysfs Interface for balloon driver Satoshi Uchida
2006-09-20 1:12 ` John Levon
2006-09-20 3:00 ` Satoshi Uchida
2006-09-20 15:20 ` John Levon
2006-09-20 18:26 ` Anthony Liguori
2006-09-20 23:23 ` Ian Pratt
2006-09-20 23:29 ` John Levon
2006-09-20 23:40 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 2:15 Satoshi Uchida
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=4511D15F.90904@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=levon@movementarian.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=s-uchida@ap.jp.nec.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.