From: Greg KH <gregkh@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Balbir Singh <balbir@in.ibm.com>
Subject: Re: [PATCH] Add Documentation for FAIR_USER_SCHED sysfs files
Date: Fri, 14 Dec 2007 14:24:58 -0800 [thread overview]
Message-ID: <20071214222458.GD29375@suse.de> (raw)
In-Reply-To: <20071212101645.GA30004@elte.hu>
On Wed, Dec 12, 2007 at 11:16:45AM +0100, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
> >
> > > > Hm, how about describing the units here? Can you put "10" in each
> > > > file and everyone will get the same share? 100? 1? 1024 seems
> > > > like an odd "share" number. Unless there is some other document you
> > > > wish to refer people to do help describe these values?
> > >
> > > It is proportional. That is, if two users have same value for shares,
> > > they will get equal bandwidth on the CPU. If they are in the ratio
> > > 1:2, then they will share it in that ratio. I've updated the patch for
> > > this. Hope it is clearer.
> >
> > thanks, applied.
>
> unless Greg wants to push this via the sysfs git tree?
Sure, I can do that, what's one more patch in my tree? :)
thanks,
greg k-h
next prev parent reply other threads:[~2007-12-14 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 2:38 [PATCH] Add Documentation for FAIR_USER_SCHED sysfs files Dhaval Giani
2007-12-12 5:35 ` Greg KH
2007-12-12 5:48 ` Dhaval Giani
2007-12-12 9:58 ` Ingo Molnar
2007-12-12 10:16 ` Ingo Molnar
2007-12-14 22:24 ` Greg KH [this message]
2007-12-15 0:11 ` patch add-documentation-for-fair_user_sched-sysfs-files.patch added to gregkh-2.6 tree gregkh
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=20071214222458.GD29375@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.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.