From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
Darren Hart <dvhltc@us.ibm.com>,
"lkml," <linux-kernel@vger.kernel.org>,
"Piggin, Nick" <piggin@cyberone.com.au>,
"Dobson, Matt" <colpatch@us.ibm.com>,
mingo@elte.hu
Subject: Re: sched_domains SD_BALANCE_FORK and sched_balance_self
Date: Wed, 10 Aug 2005 10:43:45 +1000 [thread overview]
Message-ID: <42F94DC1.5040105@yahoo.com.au> (raw)
In-Reply-To: <20050809174042.C1938@unix-os.sc.intel.com>
Siddha, Suresh B wrote:
>On Tue, Aug 09, 2005 at 03:19:58PM -0700, Martin J. Bligh wrote:
>
>>--On Tuesday, August 09, 2005 15:03:32 -0700 "Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
>>
>>
>>Balance on clone make some sort of sense, since you know they're not
>>going to exec afterwards. We've thrashed through this many times before
>>and decided that unless there was an explicit hint from userspace,
>>balance on fork was not a good thing to do in the general case. Not only
>>based on a large range of testing, but also previous experience from other
>>Unix's. What new data came forth to change this?
>>
>
>I agree with you. I will let Nick(the author) have a take at this.
>
>
Sorry I've taken a while with this. Darren, I'll reply to you soon.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2005-08-10 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 23:29 sched_domains SD_BALANCE_FORK and sched_balance_self Darren Hart
2005-08-09 22:03 ` Siddha, Suresh B
2005-08-09 22:19 ` Martin J. Bligh
2005-08-10 0:40 ` Siddha, Suresh B
2005-08-10 0:43 ` Nick Piggin [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=42F94DC1.5040105@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=colpatch@us.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=mingo@elte.hu \
--cc=piggin@cyberone.com.au \
--cc=suresh.b.siddha@intel.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.