From: Randy Dunlap <randy.dunlap@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: rt: document the risk of small values in the bandwidth settings
Date: Mon, 04 May 2009 08:39:58 -0700 [thread overview]
Message-ID: <49FF0C4E.9090807@oracle.com> (raw)
In-Reply-To: <1241451369.7620.4934.camel@twins>
Peter Zijlstra wrote:
> On Mon, 2009-05-04 at 08:34 -0700, Randy Dunlap wrote:
>>> +Fiddling with these settings can result in an unusable system, the knobs are
>>> +root only and assume root knows what he's on about.
>> I know that my English is limited, but I don't know what this means:
>> "what he's on about."
>
> Hehe, OK, how about we write it like:
>
> Fiddling with these settings can result in an unstable system, the knobs are
> root only and assumes root knows what he is doing.
>
> Does that work better for you?
Yes, thanks.
--
~Randy
prev parent reply other threads:[~2009-05-04 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 15:07 [PATCH] sched: rt: document the risk of small values in the bandwidth settings Peter Zijlstra
2009-05-04 15:34 ` Randy Dunlap
2009-05-04 15:36 ` Peter Zijlstra
2009-05-04 15:39 ` Randy Dunlap [this message]
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=49FF0C4E.9090807@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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