Hi Peter,
Ingo Molnar 于2018年11月12日周一 下午2:57写道：
>
>
> * Peter Zijlstra wrote:
>
> > I think you only need the less thing, because:
> >
> > static inline bool prio_lower(int a, int b)
> > {
> > return a > b;
> > }
>
> I'd say that should be named rt_prio_lower(), even if it's local to
>
Hi Peter,
Ingo Molnar 于2018年11月12日周一 下午2:57写道：
>
>
> * Peter Zijlstra wrote:
>
> > I think you only need the less thing, because:
> >
> > static inline bool prio_lower(int a, int b)
> > {
> > return a > b;
> > }
>
> I'd say that should be named rt_prio_lower(), even if it's local to
>
* Peter Zijlstra wrote:
> I think you only need the less thing, because:
>
> static inline bool prio_lower(int a, int b)
> {
> return a > b;
> }
I'd say that should be named rt_prio_lower(), even if it's local to
sched/rt.c, right?
Thanks,
Ingo
* Peter Zijlstra wrote:
> I think you only need the less thing, because:
>
> static inline bool prio_lower(int a, int b)
> {
> return a > b;
> }
I'd say that should be named rt_prio_lower(), even if it's local to
sched/rt.c, right?
Thanks,
Ingo
On Thu, Nov 08, 2018 at 10:15:49AM +0800, Muchun Song wrote:
> Peter Zijlstra 于2018年11月8日周四 上午1:31写道：
> > I think you only need the less thing, because:
> >
> > static inline bool prio_lower(int a, int b)
> > {
> > return a > b;
> > }
> >
> > prio_higher(a,b) := prio_lower(b,a)
> >
On Thu, Nov 08, 2018 at 10:15:49AM +0800, Muchun Song wrote:
> Peter Zijlstra 于2018年11月8日周四 上午1:31写道：
> > I think you only need the less thing, because:
> >
> > static inline bool prio_lower(int a, int b)
> > {
> > return a > b;
> > }
> >
> > prio_higher(a,b) := prio_lower(b,a)
> >
Hi Peter,
Thanks for your review.
Peter Zijlstra 于2018年11月8日周四 上午1:31写道：
>
> On Thu, Nov 08, 2018 at 12:15:05AM +0800, Muchun Song wrote:
> > We use a value to represent the priority of the RT task. But a smaller
> > value corresponds to a higher priority. If there are two RT task A and B,
> >
Hi Peter,
Thanks for your review.
Peter Zijlstra 于2018年11月8日周四 上午1:31写道：
>
> On Thu, Nov 08, 2018 at 12:15:05AM +0800, Muchun Song wrote:
> > We use a value to represent the priority of the RT task. But a smaller
> > value corresponds to a higher priority. If there are two RT task A and B,
> >
On Thu, Nov 08, 2018 at 12:15:05AM +0800, Muchun Song wrote:
> We use a value to represent the priority of the RT task. But a smaller
> value corresponds to a higher priority. If there are two RT task A and B,
> their priorities are prio_a and prio_b, respectively. If prio_a is larger
> than
On Thu, Nov 08, 2018 at 12:15:05AM +0800, Muchun Song wrote:
> We use a value to represent the priority of the RT task. But a smaller
> value corresponds to a higher priority. If there are two RT task A and B,
> their priorities are prio_a and prio_b, respectively. If prio_a is larger
> than
We use a value to represent the priority of the RT task. But a smaller
value corresponds to a higher priority. If there are two RT task A and B,
their priorities are prio_a and prio_b, respectively. If prio_a is larger
than prio_b, which means that the priority of RT task A is lower than RT
task
We use a value to represent the priority of the RT task. But a smaller
value corresponds to a higher priority. If there are two RT task A and B,
their priorities are prio_a and prio_b, respectively. If prio_a is larger
than prio_b, which means that the priority of RT task A is lower than RT
task
12 matches
Mail list logo
