From: Max Krasnyansky <maxk@qualcomm.com>
To: Paul Jackson <pj@sgi.com>
Cc: Rakib Mullick <rakib.mullick@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuset: Rework sched domains and CPU hotplug handling (take 4)
Date: Tue, 12 Aug 2008 09:39:07 -0700 [thread overview]
Message-ID: <48A1BCAB.2090502@qualcomm.com> (raw)
In-Reply-To: <20080812112750.4257544e.pj@sgi.com>
Paul Jackson wrote:
> Rakib wrote:
>> Ok, this is the second place. But, what about the first place ( I
>> mean in line 614).
>
> You present me with a clear choice.
>
> I could find your past patch, applying it to whatever it applied to,
> and look to see what was at line 614.
>
> Or I could ask you to restate your point, with enough code
> displayed so that I could understand your point just by reading
> your email.
>
> I choose the second choice. Thank-you.
I think Rakib is talking about this code
> /* Special case for the 99% of systems with one, full, sched domain */
> if (is_sched_load_balance(&top_cpuset)) {
> doms = kmalloc(sizeof(cpumask_t), GFP_KERNEL);
> if (!doms)
> goto done;
>
> dattr = kmalloc(sizeof(struct sched_domain_attr), GFP_KERNEL);
> if (dattr) {
> *dattr = SD_ATTR_INIT;
> update_domain_attr_tree(dattr, &top_cpuset);
> }
> *doms = top_cpuset.cpus_allowed;
>
> ndoms = 1;
> goto done;
> }
Which I think is perfectly fine and clear.
There are only two matches for
/attr.*=.*alloc
We covered both of them.
Max
next prev parent reply other threads:[~2008-08-12 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 21:33 [PATCH] cpuset: Rework sched domains and CPU hotplug handling (take 4) Max Krasnyansky
2008-08-11 21:38 ` Max Krasnyansky
2008-08-12 3:21 ` Rakib Mullick
2008-08-12 3:27 ` Max Krasnyansky
[not found] ` <b9df5fa10808120501i57dbd71k71b54cca0bfb2ff2@mail.gmail.com>
2008-08-12 13:48 ` Rakib Mullick
2008-08-12 16:27 ` Paul Jackson
2008-08-12 16:39 ` Max Krasnyansky [this message]
2008-08-12 17:12 ` Rakib Mullick
2008-08-12 3:33 ` Paul Jackson
2008-08-11 23:31 ` Paul Jackson
2008-08-14 9:24 ` Ingo Molnar
2008-08-14 11:16 ` Ingo Molnar
2008-08-14 18:21 ` Max Krasnyansky
2008-08-20 6:44 ` [input layer, lockdep warning] " Ingo Molnar
2008-08-20 13:08 ` Dmitry Torokhov
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=48A1BCAB.2090502@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rakib.mullick@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox