[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fc220af-3f9d-416f-b2f4-a50281cd5f4a@efficios.com>
Date: Wed, 29 Oct 2025 11:31:44 -0400
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
 Gabriele Monaco <gmonaco@...hat.com>, Michael Jeanson
 <mjeanson@...icios.com>, Jens Axboe <axboe@...nel.dk>,
 "Paul E. McKenney" <paulmck@...nel.org>,
 "Gautham R. Shenoy" <gautham.shenoy@....com>,
 Florian Weimer <fweimer@...hat.com>, Tim Chen <tim.c.chen@...el.com>,
 Yury Norov <yury.norov@...il.com>, Shrikanth Hegde <sshegde@...ux.ibm.com>
Subject: Re: [patch V3 02/20] sched/mmcid: Use proper data structures
On 2025-10-29 09:08, Thomas Gleixner wrote:
> Having a lot of CID functionality specific members in struct task_struct
> and struct mm_struct is not really making the code easier to read.
> 
> Encapsulate the CID specific parts in data structures and keep them
> seperate from the stuff they are embedded in.
seperate -> separate
Other than this nit:
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
Powered by blists - more mailing lists
 
