From: Rene Herman <rene.herman@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Christoph Lameter <clameter@sgi.com>
Subject: Re: Are we properly prepared to handle 3 Socket setups?
Date: Sun, 12 Aug 2007 22:00:52 +0200 [thread overview]
Message-ID: <46BF66F4.9030106@gmail.com> (raw)
In-Reply-To: <20070812013519.a5d5d59b.akpm@linux-foundation.org>
On 08/12/2007 10:35 AM, Andrew Morton wrote:
> On Sun, 12 Aug 2007 05:17:10 +0200 Rene Herman <rene.herman@gmail.com> wrote:
>> The line just below where it does that _does_ seem to have a problem:
>>
>> /*
>> * Maximum threshold is 125
>> */
>> threshold = min(125, threshold);
>>
>> as either the comment or the code is wrong and it seems it's the code. Added
>> Andrew Morton to the CC for that.
>
> Yes, that's inconsistent. And looking at Christoph's df9ecaba it's unclear
> whether the comment is wrong or the code is wrong. The code is wrong, I
> expect.
Extremely friendly of you to pretend I wasn't being thick at all but don't
worry, I can take it. Anyways, since Christoph wasn't in CC on that one:
On 08/12/2007 05:29 AM, Roland Dreier wrote:
> What's the problem? That line sets threshold to the smaller of the
> current value or 125, which is exactly what one would want to do if the
> maximum value is 125. Just do a couple of examples: eg if threshold is
> 100 going into that line, then the value is left alone; if threshold is
> 150 then it gets set to 125; and that seems exactly correct.
Rene.
next prev parent reply other threads:[~2007-08-12 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 1:08 Are we properly prepared to handle 3 Socket setups? Jesper Juhl
2007-08-12 1:27 ` Rene Herman
2007-08-12 1:52 ` Jesper Juhl
2007-08-12 3:17 ` Rene Herman
2007-08-12 3:29 ` Roland Dreier
2007-08-12 3:36 ` Rene Herman
2007-08-12 8:35 ` Andrew Morton
2007-08-12 20:00 ` Rene Herman [this message]
2007-08-13 20:44 ` Christoph Lameter
2007-08-12 7:24 ` Paul Mundt
2007-08-12 8:41 ` Willy Tarreau
2007-08-12 11:46 ` Andi Kleen
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=46BF66F4.9030106@gmail.com \
--to=rene.herman@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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