From: Max Krasnyansky <maxk@qualcomm.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] CPU isolation extensions
Date: Thu, 07 Feb 2008 10:22:32 -0800 [thread overview]
Message-ID: <47AB4C68.1080308@qualcomm.com> (raw)
In-Reply-To: <20080207121040.42efad60.pj@sgi.com>
Paul Jackson wrote:
> Max - Andrew wondered if the rt tree had seen the
> code or commented it on it. What became of that?
I just replied to Andrew. It's not an RT feature per se.
And yes Peter CC'ed RT folks. You probably did not get a chance to read all replies.
They had some questions/concerns and stuff. I believe I answered/clarified all of them.
> My two cents isn't worth a plug nickel here, but
> I'm inclined to nod in agreement when Linus wants
> to see these patches get some more exposure before
> going into Linus's tree. ... what's the hurry?
No hurry I guess. I did mentioned in the introductory email that I've been maintaining
this stuff for awhile now. SLAB patches used to be messy, with new SLUB the mess goes away.
CFS handles CPU hotplug much better than O(1), cpu hotplug is needed to be able to change
isolated bit from sysfs. That's why I think it's a good time to merge.
I don't mind of course if we put this stuff in -mm first. Although first part of the patchset
(ie exporting isolated map, sysfs interface, etc) seem very simple and totally not controversial.
Stop machine patch is really the only thing that may look suspicious.
Max
next prev parent reply other threads:[~2008-02-07 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 5:32 [git pull] CPU isolation extensions Max Krasnyansky
2008-02-07 5:58 ` Andrew Morton
2008-02-07 7:59 ` Paul Jackson
2008-02-07 8:12 ` Andrew Morton
2008-02-07 18:14 ` Max Krasnyansky
2008-02-07 18:02 ` Max Krasnyansky
2008-02-07 18:10 ` Paul Jackson
2008-02-07 18:22 ` Max Krasnyansky [this message]
2008-02-07 17:22 ` Max Krasnyansky
2008-02-07 19:26 ` Andrew Morton
2008-02-07 17:06 ` Linus Torvalds
2008-02-07 17:36 ` Max Krasnyansky
2008-02-07 19:51 ` Ingo Molnar
2008-02-08 0:38 ` Max Krasnyansky
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=47AB4C68.1080308@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=torvalds@linux-foundation.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