All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: dino@in.ibm.com
Cc: Simon.Derr@bull.net, nickpiggin@yahoo.com.au,
	linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
	colpatch@us.ibm.com, dipankar@in.ibm.com, akpm@osdl.org
Subject: Re: [Lse-tech] Re: [RFT PATCH] Dynamic sched domains (v0.6)
Date: Wed, 18 May 2005 14:02:13 -0700	[thread overview]
Message-ID: <20050518140213.39f59450.pj@sgi.com> (raw)
In-Reply-To: <20050518180652.GA4293@in.ibm.com>

Dinakar wrote:
> >  * The name 'nodemask' for the cpumask_t of CPUs that are siblings to CPU i
> >    is a bit confusing (yes, that name was already there).  How about
> >    something like 'siblings' ?
> 
> Not sure which code you are referring to here ?? I dont see any nodemask
> referring to SMT siblings ? 

This comment was referring to lines such as the following, which appear
a few places in your patch (though not lines you wrote, just nearby
lines, in all but one case):

 		cpumask_t nodemask = node_to_cpumask(cpu_to_node(i));

I was thinking to change such a line to:

 		cpumask_t sibling = node_to_cpumask(cpu_to_node(i));

However, it is no biggie, and since it is not in your actual new
code, probably should not be part of your patch anyway.

There is one place, arch_destroy_sched_domains(), where you added such a
line, but there you should probably use the same 'nodemask' name as the
other couple of places, unless and until these places change together.

So bottom line - nevermind this comment.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401

  reply	other threads:[~2005-05-18 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  4:10 [RFT PATCH] Dynamic sched domains (v0.6) Dinakar Guniguntala
2005-05-17  4:12 ` [PATCH 2/3] " Dinakar Guniguntala
2005-05-17  6:25   ` Nick Piggin
2005-05-17  9:35     ` Dinakar Guniguntala
2005-05-17  4:14 ` [PATCH 3/3] " Dinakar Guniguntala
2005-05-18  5:53 ` [RFT PATCH] " Paul Jackson
2005-05-18 18:06   ` [Lse-tech] " Dinakar Guniguntala
2005-05-18 21:02     ` Paul Jackson [this message]
2005-05-18 21:04     ` Paul Jackson
2005-05-18 21:05     ` 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=20050518140213.39f59450.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=colpatch@us.ibm.com \
    --cc=dino@in.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=nickpiggin@yahoo.com.au \
    /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.