[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c704568d-16d1-bbd8-2b59-1d719f2bcf8c@wanadoo.fr>
Date: Fri, 28 Apr 2023 09:33:01 +0200
From: Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: Chaitanya Kulkarni <chaitanyak@...dia.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sagi Grimberg <sagi@...mberg.me>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"kbusch@...nel.org" <kbusch@...nel.org>
Subject: Re: [PATCH] nvmet: Reorder fields in 'struct nvmet_ns'
Le 28/04/2023 à 01:12, Chaitanya Kulkarni a écrit :
> (+Keith, for host side)
>> ---
>> More aggressive grouping could be done to be more future proof, but the
>> way the struct nvmet_ns is written suggest that some fields should be
>> kept together. So keep grouping as-is.
>>
>>
>
> you can send RFC and I'll be happy to take a look if it's going
> have any benefit, it will take some time though..
>
> for host side :-
>
> while you are at it, it might be useful to take a look at the structures
> that are accessed in the fast path on the host side ?
Ok, why not, but can you help identifying these structures or places
considered as fast path?
CJ
>
> unless there is some reason for not doing that ...
>
> -ck
>
>
Powered by blists - more mailing lists