netdev - Re: [PATCH v2 net-next 0/7] net: foo-over-udp (fou)

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: <CAJ3xEMhax-S1KneM-cpRS9r4yi==JwqaGtMYJ127Ka2tynhHMw@mail.gmail.com>
Date:	Tue, 16 Sep 2014 23:04:30 +0300
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Tom Herbert <therbert@...gle.com>
Cc:	David Miller <davem@...emloft.net>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 net-next 0/7] net: foo-over-udp (fou)

On Tue, Sep 16, 2014 at 6:00 PM, Tom Herbert <therbert@...gle.com> wrote:
> [...] Fortunately, we'll be able to code
> around mosts of the limitations of deployed NICs that don't implement
> generic mechanisms (with UDP RSS, checksum conversions,  remote
> checksum offload) [...]

So UDP RSS is a clear requirement and NICs have it by now.

Re checksum conversions, I assume you mean the ability on the RX path
to report CHECKSUM_COMPLETE on any sort of IP packet potentially
having multiple encapsulations, right? how would you phrase (and
model) the other way around, e.g what is the generic requirement on
the TX path w.r.t checksum offload?

And I wasn't sure what do you mean by remote checksum offload, can you clarify?

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