Peter, Dario,
This is a little late in the day, but I think it's an important point
to just check before this API goes final.
> SYNOPSIS
> #include <sched.h>
>
> struct sched_attr {
> u32 size;
>
> u32 sched_policy;
> u64 sched_flags;
[...]
> };
>
> int sched_setattr(pid_t pid, const struct sched_attr *attr);
>
> int sched_getattr(pid_t pid, const struct sched_attr *attr, unsigned
> int size);
So, I that there's a flags field in the structure, which allows for
some extensibility for these calls in the future. However, is it
worthwhile to consider adding a 'flags' argument in the base signature
of either of these calls, to allow for some possible extensions in the
future. (See http://lwn.net/SubscriberLink/585415/7b905c0248a158a2/ ).
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
