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-next>] [day] [month] [year] [list]
Date: Sat, 25 May 2024 16:43:20 +0000
From: "Jain, Vipin" <Vipin.Jain@....com>
To: "Singhai, Anjali" <anjali.singhai@...el.com>, "Hadi Salim, Jamal"
	<jhs@...atatu.com>, Jakub Kicinski <kuba@...nel.org>
CC: Paolo Abeni <pabeni@...hat.com>, Alexei Starovoitov
	<alexei.starovoitov@...il.com>, Network Development <netdev@...r.kernel.org>,
	"Chatterjee, Deb" <deb.chatterjee@...el.com>, "Limaye, Namrata"
	<namrata.limaye@...el.com>, tom Herbert <tom@...anda.io>, Marcelo Ricardo
 Leitner <mleitner@...hat.com>, "Shirshyad, Mahesh"
	<Mahesh.Shirshyad@....com>, "Osinski, Tomasz" <tomasz.osinski@...el.com>,
	Jiri Pirko <jiri@...nulli.us>, Cong Wang <xiyou.wangcong@...il.com>, "David
 S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Vlad
 Buslov <vladbu@...dia.com>, Simon Horman <horms@...nel.org>, Khalid Manaa
	<khalidm@...dia.com>, Toke Høiland-Jørgensen
	<toke@...hat.com>, Victor Nogueira <victor@...atatu.com>, "Tammela, Pedro"
	<pctammela@...atatu.com>, "Daly, Dan" <dan.daly@...el.com>, Andy Fingerhut
	<andy.fingerhut@...il.com>, "Sommers, Chris" <chris.sommers@...sight.com>,
	Matty Kadosh <mattyk@...dia.com>, bpf <bpf@...r.kernel.org>, "lwn@....net"
	<lwn@....net>
Subject: Re: On the NACKs on P4TC patches

[AMD Official Use Only - AMD Internal Distribution Only]

My apologies, earlier email used html and was blocked by the list...
My response at the bottom as "VJ>"

________________________________________
From: Jain, Vipin <Vipin.Jain@....com>
Sent: Friday, May 24, 2024 2:28 PM
To: Singhai, Anjali <anjali.singhai@...el.com>; Hadi Salim, Jamal <jhs@...atatu.com>; Jakub Kicinski <kuba@...nel.org>
Cc: Paolo Abeni <pabeni@...hat.com>; Alexei Starovoitov <alexei.starovoitov@...il.com>; Network Development <netdev@...r.kernel.org>; Chatterjee, Deb <deb.chatterjee@...el.com>; Limaye, Namrata <namrata.limaye@...el.com>; tom Herbert <tom@...anda.io>; Marcelo Ricardo Leitner <mleitner@...hat.com>; Shirshyad, Mahesh <Mahesh.Shirshyad@....com>; Osinski, Tomasz <tomasz.osinski@...el.com>; Jiri Pirko <jiri@...nulli.us>; Cong Wang <xiyou.wangcong@...il.com>; David S. Miller <davem@...emloft.net>; Eric Dumazet <edumazet@...gle.com>; Vlad Buslov <vladbu@...dia.com>; Simon Horman <horms@...nel.org>; Khalid Manaa <khalidm@...dia.com>; Toke Høiland-Jørgensen <toke@...hat.com>; Victor Nogueira <victor@...atatu.com>; Tammela, Pedro <pctammela@...atatu.com>; Daly, Dan <dan.daly@...el.com>; Andy Fingerhut <andy.fingerhut@...il.com>; Sommers, Chris <chris.sommers@...sight.com>; Matty Kadosh <mattyk@...dia.com>; bpf <bpf@...r.kernel.org>; lwn@....net <lwn@....net>
Subject: Re: On the NACKs on P4TC patches

[AMD Official Use Only - AMD Internal Distribution Only]


I can ascertain (from AMD) that we have stated interest in, and are in full support of P4TC.

Happy to elaborate more if needed.

Thank you,
Vipin Jain
Sr Fellow Engineer, AMD
________________________________________
From: Singhai, Anjali <anjali.singhai@...el.com>
Sent: Wednesday, May 22, 2024 5:30 PM
To: Hadi Salim, Jamal <jhs@...atatu.com>; Jakub Kicinski <kuba@...nel.org>
Cc: Paolo Abeni <pabeni@...hat.com>; Alexei Starovoitov <alexei.starovoitov@...il.com>; Network Development <netdev@...r.kernel.org>; Chatterjee, Deb <deb.chatterjee@...el.com>; Limaye, Namrata <namrata.limaye@...el.com>; tom Herbert <tom@...anda.io>; Marcelo Ricardo Leitner <mleitner@...hat.com>; Shirshyad, Mahesh <Mahesh.Shirshyad@....com>; Osinski, Tomasz <tomasz.osinski@...el.com>; Jiri Pirko <jiri@...nulli.us>; Cong Wang <xiyou.wangcong@...il.com>; David S. Miller <davem@...emloft.net>; Eric Dumazet <edumazet@...gle.com>; Vlad Buslov <vladbu@...dia.com>; Simon Horman <horms@...nel.org>; Khalid Manaa <khalidm@...dia.com>; Toke Høiland-Jørgensen <toke@...hat.com>; Victor Nogueira <victor@...atatu.com>; Tammela, Pedro <pctammela@...atatu.com>; Jain, Vipin <Vipin.Jain@....com>; Daly, Dan <dan.daly@...el.com>; Andy Fingerhut <andy.fingerhut@...il.com>; Sommers, Chris <chris.sommers@...sight.com>; Matty Kadosh <mattyk@...dia.com>; bpf <bpf@...r.kernel.org>; lwn@....net <lwn@....net>
Subject: RE: On the NACKs on P4TC patches

Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.


On Wed, May 22, 2024 at 6:19 PM Jakub Kicinski <kuba@...nel.org> wrote:

>> AFAICT there's some but not very strong support for P4TC,

On Wed, May 22, 2024 at 4:04 PM Jamal Hadi Salim <jhs@...atatu.com > wrote:
>I dont agree. Paolo asked this question and afaik Intel, AMD (both build P4-native NICs) and the folks interested in the MS DASH project >responded saying they are in support. Look at who is being Cced. A lot of these folks who attend biweekly discussion calls on P4TC. >Sample:
>https://lore.kernel.org/netdev/IA0PR17MB7070B51A955FB8595FFBA5FB965E2@IA0PR17MB7070.namprd17.prod.outlook.com/

FWIW, Intel is in full support of P4TC as we have stated several times in the past.

VJ> I can ascertain (from AMD) that we have stated interest in, and are in full support of P4TC. Happy to elaborate more if needed.
VJ> Thanks, Vipin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ