From: Paul Jackson <pj@sgi.com>
To: dino@in.ibm.com
Cc: Simon.Derr@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Cpuset: remove useless sched domain line
Date: Wed, 18 Oct 2006 22:12:52 -0700 [thread overview]
Message-ID: <20061018221252.47861641.pj@sgi.com> (raw)
In-Reply-To: <20061018172422.GA7885@in.ibm.com>
Dinakar wrote:
> I dont think this is a valid optimization.
I probably don't agree, but I think there might be a better way to deal
with this line of code - remove the entire routine ;).
I have a patch set I am about to send in to lkml for comment, that
removes the entire mechanism connecting cpusets to sched domains,
replacing it with a much simpler (even I can understand) mechanism to
update the isolated_cpu_map on the fly.
If that flies, then this present patch becomes obsolete and irrelevant.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-10-19 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 4:55 [RFC] Cpuset: remove useless sched domain line Paul Jackson
2006-10-18 17:24 ` Dinakar Guniguntala
2006-10-19 5:12 ` Paul Jackson [this message]
2006-10-22 9:16 ` Paul Jackson
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=20061018221252.47861641.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=dino@in.ibm.com \
--cc=linux-kernel@vger.kernel.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