From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Kirill Korotaev <dev@sw.ru>
Cc: Paul Menage <menage@google.com>,
Linux Containers <containers@lists.osdl.org>,
Pavel Emelianov <xemul@openvz.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch -rss] Make RSS accounting display more user friendly
Date: Tue, 26 Jun 2007 08:54:00 -0400 [thread overview]
Message-ID: <46810C68.7020603@linux.vnet.ibm.com> (raw)
In-Reply-To: <4681090A.6030805@sw.ru>
Kirill Korotaev wrote:
> Paul Menage wrote:
>> On 6/22/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>>
>>> The problem with input in bytes is that the user will have to ensure
>>> that the input is
>>> a multiple of page size, which implies that she would need to use the
>>> calculator every time.
>>>
>>
>> Having input in bytes seems pretty natural to me. Why not just have
>> the RSS controller round the input to the nearest page (or whatever
>> granularity of memory the controller is able to limit at)?
>
> totally agree with Paul.
>
> Kirill
>
Kirill
If someone assigns a rss_limit of 1 byte and sees a usage of 1 page,
won't that be confusing. But having said that it's not a big
change, it should be easy to accommodate.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-06-26 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 15:46 [patch -rss] Make RSS accounting display more user friendly Balbir Singh
2007-06-21 19:17 ` Paul Menage
2007-06-22 2:09 ` Pavel Emelianov
2007-06-22 15:39 ` Paul Menage
2007-06-23 3:48 ` Balbir Singh
2007-06-25 7:19 ` Paul Menage
2007-06-26 12:39 ` Kirill Korotaev
2007-06-26 12:54 ` Balbir Singh [this message]
2007-06-26 14:05 ` Kirill Korotaev
2028-02-27 7:39 ` Balbir Singh
2007-07-09 11:38 ` Peter Zijlstra
2007-07-10 4:44 ` Balbir Singh
2007-07-10 15:29 ` Randy Dunlap
2007-07-10 15:40 ` Balbir Singh
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=46810C68.7020603@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=xemul@openvz.org \
/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