On 09/14, Roland McGrath wrote:
>
> > But can't we move ->reporting from utrace to engine? This saves a word
> > in task_struct. Yes, this adds the same word to engine, but we should
> > optimize the common untraced case.
>
> That will be optimized properly when we move struct utrace out of task_st
> But can't we move ->reporting from utrace to engine? This saves a word
> in task_struct. Yes, this adds the same word to engine, but we should
> optimize the common untraced case.
That will be optimized properly when we move struct utrace out of task_struct.
Inflating the size of struct utrace_e
I still need to review (and understand ;) the ->reporting logic/barriers
and continue the related discussion.
But can't we move ->reporting from utrace to engine? This saves a word
in task_struct. Yes, this adds the same word to engine, but we should
optimize the common untraced case.
Or do you h
