netdev - Re: [PATCH 00/10 net-next] Introduce per interface ipv4 statistics

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: <20111216.132746.627284368195962110.davem@davemloft.net>
Date:	Fri, 16 Dec 2011 13:27:46 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	igorm@....rs, netdev@...r.kernel.org
Subject: Re: [PATCH 00/10 net-next] Introduce per interface ipv4 statistics

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Fri, 16 Dec 2011 16:41:20 +0100

> 1) Why is it needed ? Any RFC requires this bloat ?

I'm not allowing something like this into ipv4, there are too many
terrible side effects in ipv6 because we do it there.

The mere necessity of having to have some device handle at every single packet
processing spot is incredibly painful, and makes changes in the ipv6 packet
paths 10 times more difficult than they otherwise would be.

I'm not allowing this difficulty to be added to the ipv4 side as well.
--
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