linux-kernel - Re: [PATCH net-next RFC] net: increase LL_MAX

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150916.105936.2275139635170756984.davem@davemloft.net>
Date:	Wed, 16 Sep 2015 10:59:36 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	David.Laight@...LAB.COM
Cc:	haiyangz@...rosoft.com, vkuznets@...hat.com,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	kys@...rosoft.com, jasowang@...hat.com
Subject: Re: [PATCH net-next RFC] net: increase LL_MAX_HEADER for Hyper-V

From: David Laight <David.Laight@...LAB.COM>
Date: Wed, 16 Sep 2015 16:25:03 +0000

> Am I right in thinking this is adding an extra 96 unused bytes to the front
> of almost all skb just so that hyper-v can make its link level header
> contiguous with whatever follows (IP header ?).
> 
> Doesn't sound ideal.

Agreed, this is rediculous, and the entire stack will incur this cost
just because hyperv is enabled in the kernel config.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/