Re: [PATCH v3] sched: print information about scheduling granularity

[Dario Faggioli <dfaggioli@xxxxxxxx>]

On Wed, 2020-04-22 at 12:50 +0200, Jan Beulich wrote:
> On 22.04.2020 11:30, Sergey Dyasli wrote:
> > +struct sched_gran_name {
> > +    enum sched_gran mode;
> > +    const char *name;
> > +};
> > +
> > +static const struct sched_gran_name sg_name[] = {
> > +    {SCHED_GRAN_cpu, "cpu"},
> > +    {SCHED_GRAN_core, "core"},
> > +    {SCHED_GRAN_socket, "socket"},
> > +};
> 
> Personally I think that in cases like this one it is more
> (space) efficient to use char[8] or so for the second
> struct member.
>
Yeah, I think that is actually better.

Sergey, can you do it like this?

Thanks and Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)

Attachment: signature.asc
Description: This is a digitally signed message part