[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140505.230925.403754888653633720.davem@davemloft.net>
Date: Mon, 05 May 2014 23:09:25 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: andi@...stfloor.org
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
tom.zanussi@...ux.intel.com, ak@...ux.intel.com
Subject: Re: [PATCH 21/24] net, diet: Make packet tpacket/mmap/fanout/rings
optional
From: Andi Kleen <andi@...stfloor.org>
Date: Mon, 5 May 2014 15:26:10 -0700
> From: Andi Kleen <ak@...ux.intel.com>
>
> Many DHCP clients need basic packet sockets, but they don't need
> the fancy zero copy packet capture code, like tpacket, mmap, rings,
> fanouts. This is quite substantial code, so it's worthwhile to
> make it optional
>
> Worth nearly 10k code.
>
> text data bss dec hex filename
> 952827 71874 25352 1050053 1005c5 net/built-in.o-with-packet-mmap
> 943211 71810 25352 1040373 fdff5 net/built-in.o-wo-packet-mmap
>
> Signed-off-by: Andi Kleen <ak@...ux.intel.com>
Sorry, I'm not applying this either.
Small systems use packet generation and reception tools commonly, and
the only sane way to do so is with tpacket.
--
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