[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80074375-2d37-d9b9-afbe-1f3d1db4a41f@grimberg.me>
Date: Wed, 3 Feb 2021 00:56:35 -0800
From: Sagi Grimberg <sagi@...mberg.me>
To: Or Gerlitz <gerlitz.or@...il.com>, Christoph Hellwig <hch@....de>,
Keith Busch <kbusch@...nel.org>, axboe@...com
Cc: Boris Pismenny <borisp@...lanox.com>, smalin@...vell.com,
yorayz@...dia.com, boris.pismenny@...il.com,
Ben Ben-Ishay <benishay@...lanox.com>,
Yoray Zack <yorayz@...lanox.com>,
linux-nvme@...ts.infradead.org, David Miller <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Linux Netdev List <netdev@...r.kernel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
David Ahern <dsahern@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Or Gerlitz <ogerlitz@...lanox.com>, benishay@...dia.com,
Saeed Mahameed <saeedm@...dia.com>,
Or Gerlitz <ogerlitz@...dia.com>
Subject: Re: [PATCH v3 net-next 07/21] nvme-tcp: Add DDP data-path
>> Given how much ddp code there is can you split it into a separate file?
>
> mmm, do we need to check the preferences or get to a consensus among
> the maintainers for that one?
Not sure if moving it would be better here. Given that the ddp code is
working directly on nvme-tcp structs we'll need a new shared header
file..
Its possible to do, but I'm not sure the end result will be better..
Powered by blists - more mailing lists