public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	mingo@redhat.com, paul@paulmenage.org
Subject: Re: [PATCH 0/5] cpusets: dynamical scheduler domain flags
Date: Mon, 23 Jul 2012 10:30:59 +0800	[thread overview]
Message-ID: <500CB763.9020802@linux.vnet.ibm.com> (raw)
In-Reply-To: <1342802550.2583.12.camel@twins>

On 07/21/2012 12:42 AM, Peter Zijlstra wrote:
> On Tue, 2012-07-17 at 17:03 +0800, Michael Wang wrote:
>> This patch set provide a way for user to dynamically configure the scheduler
>> domain flags, which usually to be static. 
> 
> NAK.. you don't get to expose all this nonsense in a 'stable' ABI.
> 
> You shouldn't need to prod at them to begin with.

So is that means expose those domain flags to user is a bad idea at all?

Is this caused by that people don't need such feature or this feature
has do harm to kernel's stability?(it could be not...)

Regards,
Michael Wang

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  reply	other threads:[~2012-07-23  2:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  9:03 [PATCH 0/5] cpusets: dynamical scheduler domain flags Michael Wang
2012-07-20 16:42 ` Peter Zijlstra
2012-07-23  2:30   ` Michael Wang [this message]
2012-07-23  4:28     ` Mike Galbraith
2012-07-23  4:58       ` Michael Wang

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=500CB763.9020802@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul@paulmenage.org \
    --cc=peterz@infradead.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