netdev - Re: Re: [PATCH 13/23 v3] mlx4: Unicast Loopback support

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>] [day] [month] [year] [list]

Date:	Tue, 16 Feb 2010 08:45:43 +0200
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	Yevgeny Petrilin <yevgenyp@...lanox.co.il>
Cc:	Roland Dreier <rdreier@...co.com>, netdev@...r.kernel.org,
	liranl@...lanox.co.il, Tziporet Koren <tziporet@...lanox.co.il>
Subject: Re: Re: [PATCH 13/23 v3] mlx4: Unicast Loopback support

Yevgeny Petrilin <yevgenyp@...lanox.co.il> wrote:
> Or Gerlitz [or.gerlitz@...il.com] wrote:

>> I wasn't sure what is the use case here, isn't loopback handled by higher levels at the network stack?

> The use case is two VMs using the same physical adapter.

I am still not with you: are you referring to the case where each VM
is being served by a
different VF? in that case, the VF driver (mlx4_en) has no way to know
its a "loopback" packet,
and switching between VFs can be programmed to the PF by the PF driver
(modified mlx4_core).

If you are talking to the case both VMs are being served by the same
PCI function --> same NIC
then again, loopback is handled in higher level.

Is there a 3rd use case?

Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html