netdev - Re: [PATCH v25 00/20] nvme-tcp receive offloads

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <475934b5-4e41-44c9-92c7-50ad04fa70d6@nvidia.com>
Date: Wed, 26 Jun 2024 20:10:41 +0000
From: Chaitanya Kulkarni <chaitanyak@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Sagi Grimberg <sagi@...mberg.me>, "linux-nvme@...ts.infradead.org"
	<linux-nvme@...ts.infradead.org>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>, "hch@....de" <hch@....de>, "kbusch@...nel.org"
	<kbusch@...nel.org>, "axboe@...com" <axboe@...com>, "davem@...emloft.net"
	<davem@...emloft.net>, Shai Malin <smalin@...dia.com>, "malin1024@...il.com"
	<malin1024@...il.com>, Yoray Zack <yorayz@...dia.com>, Jason Gunthorpe
	<jgg@...dia.com>, Tariq Toukan <tariqt@...dia.com>, Max Gurtovoy
	<mgurtovoy@...dia.com>, Gal Shalom <galshalom@...dia.com>, Boris Pismenny
	<borisp@...dia.com>, Or Gerlitz <ogerlitz@...dia.com>, Aurelien Aptel
	<aaptel@...dia.com>
Subject: Re: [PATCH v25 00/20] nvme-tcp receive offloads

Jakub,

On 6/26/24 12:43, Jakub Kicinski wrote:
> On Wed, 26 Jun 2024 19:34:50 +0000 Chaitanya Kulkarni wrote:
>>> I'm not sure we're on the same page. The ask is to run the tests on
>>> the netdev testing branch, at 12h cadence, and generate a simple JSON
>>> file with results we can ingest into our reporting. Extra points to
>>> reporting it to KCIDB. You mention "framework that is focused on
>>> netdev", IDK what you mean.
>> just to clarify are you saying that you are want us to :-
>>
>> 1. Pull the latest changes from netdev current development branch
>>      every 12 hours.
> Small but important difference - testing branch, not development branch.
> There may be malicious code in that branch, since its not fully
> reviewed.
>

indeed, we will ask you for a right branch once we have things in place ...

>> 2. Run blktests on the HEAD of that branch.
> Or some subset of blktest, if the whole run takes too long.

we need to target nvme-tcp blktests, I believe we can't skip any of those
tests, if needed we can do some optimizations on testing side to speed up
things ..

>> 3. Gather those results into JASON file.
>> 4. Post it publicly accessible to you.
> Yes.

sounds good ..

>> I didn't understand the "ingest into our reporting part", can you
>> please clarify ?
> You just need to publish the JSON files with results, periodically
> (publish = expose somewhere we can fetch from over HTTP).
> The ingestion part is on our end.

Thanks for the clarification, we will get back to you before mid next week.

We are actively building and running blktests so we are committed to
testing.

My other question is how can we make progress on getting this
code merge ? (assuming that we do all the above, but it will take some time
to build the infra) IOW, can we get this code merge before we build above
infrastructure ?

If we can, which repo it should go through ? nvme or netdev ?

-ck