public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <david.ahern@oracle.com>
To: Mike Galbraith <efault@gmx.de>
Cc: peterz@infradead.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched: Add cpu based entries to debugfs
Date: Sun, 29 Mar 2015 20:48:37 -0600	[thread overview]
Message-ID: <5518B985.5020906@oracle.com> (raw)
In-Reply-To: <1427682744.3185.16.camel@gmx.de>

On 3/29/15 8:32 PM, Mike Galbraith wrote:
> On Sun, 2015-03-29 at 22:13 -0400, David Ahern wrote:
>
>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> index 62671f53202a..b4d8d0c8260e 100644
>> --- a/kernel/sched/core.c
>> +++ b/kernel/sched/core.c
>> @@ -268,12 +268,173 @@ static const struct file_operations sched_feat_fops = {
>>   	.release	= single_release,
>>   };
>>
>> +static const char * const sd_flag_names[] = {
>> +	"load-balance",
>> +	"new-idle",
>> +	"exec",
>> +	"fork",
>> +	"wake",
>> +	"affine",
>> +	"",
>> +	"cpu-capacity",
>> +	"power-domain",
>> +	"share-pkg-resources",
>> +	"serialize",
>> +	"asym-packing",
>> +	"prefer-sibling",
>> +	"overlap",
>> +	"numa",
>> +	"",
>> +};
>
> That's wrong with the names readers will want to grep for?

I just found lower-case easier on the eyes. I could change this list to 
correspond to the SD_XXXXX defines. Certainly something that more 
programmatically correlates the macros (bit positions) and the names 
would be better.

David


  reply	other threads:[~2015-03-30  2:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  2:13 [RFC PATCH] sched: Add cpu based entries to debugfs David Ahern
2015-03-30  2:32 ` Mike Galbraith
2015-03-30  2:48   ` David Ahern [this message]
2015-03-30  3:08     ` Mike Galbraith
2015-03-30 13:03       ` David Ahern
2015-03-30 14:45         ` Mike Galbraith
2015-03-30  7:44 ` Peter Zijlstra
2015-03-30  8:26   ` Mike Galbraith
2015-03-30  8:28     ` Peter Zijlstra
2015-03-30  8:43       ` Mike Galbraith
2015-03-30  9:18         ` Peter Zijlstra
2015-03-31  9:13           ` Ingo Molnar
2015-04-06  2:10             ` David Ahern
2015-04-06  4:04               ` Mike Galbraith
2015-03-30 13:02   ` David Ahern

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=5518B985.5020906@oracle.com \
    --to=david.ahern@oracle.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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