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
| ||
|
Date: Tue, 7 Oct 2014 13:28:01 -0700 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: David Miller <davem@...emloft.net> Cc: Tom Herbert <therbert@...gle.com>, Jesse Gross <jesse@...ira.com>, "gerlitz.or@...il.com" <gerlitz.or@...il.com>, Alexander Duyck <alexander.h.duyck@...el.com>, John Fastabend <john.r.fastabend@...el.com>, Jeff Kirsher <jeffrey.t.kirsher@...el.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Thomas Graf <tgraf@...g.ch>, Pravin Shelar <pshelar@...ira.com>, Andy Zhou <azhou@...ira.com> Subject: Re: [PATCH] net: Add ndo_gso_check On Tue, Oct 7, 2014 at 11:47 AM, David Miller <davem@...emloft.net> wrote: > > I am totally against boolean "yes/no" protocol specific checksum > validation by HW. > > It's not faster. You have to look at the pseudo-header and bring it into > the CPU cache _anyways_, so negating it and 2's complementing it into > the CHECKSUM_COMPLETE value for validation is free. > > There is no performance advantage whatsoever to use another checksumming > scheme. ok, forget faster/slower argument for a second. Why is it a bad thing to have HW verifying checksums? Tom's argument of difficult bugs in firmware is valid, but there can be bugs in hw too and in kernel stack... Also NICs do verify csum already. What are we saying here? Stop doing it? I can trust only kernel stack to verify csum? btw, just remembered why COMPLETE is slow in the datacenter... virtio doesn't have support for it. Packets going into tap without VIRTIO_NET_HDR_F_DATA_VALID, so guests have to do whole packet csum. -- 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
Powered by blists - more mailing lists