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
| ||
|
Message-ID: <20230522141545.408f61b0@kernel.org> Date: Mon, 22 May 2023 14:15:45 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Shay Drory <shayd@...dia.com> Cc: Saeed Mahameed <saeed@...nel.org>, "David S. Miller" <davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>, Saeed Mahameed <saeedm@...dia.com>, <netdev@...r.kernel.org>, Tariq Toukan <tariqt@...dia.com>, Moshe Shemesh <moshe@...dia.com> Subject: Re: [PATCH net-next] net/mlx5: Introduce SF direction On Mon, 22 May 2023 15:47:15 +0300 Shay Drory wrote: > > What does it mean that an SF is "facing" the network? > > Facing the physical wire, like an UPLINK vport. > > > Why can't the device automatically "optimize" the hairpin? > > Our FW/HW can do steering optimization if we know the direction in advance. > > > Or SF1 / SF2 will be uni-directional after this patch? > > No. every SF will continue to be bi-directional. the change will only > affect steering optimization. I'm not going to claw the details out of you. AFAICT this sounds like a lazy knob forcing the user to configure something that could be done automatically. Consider it rejected.
Powered by blists - more mailing lists