netdev - Re: Re-queueing of skb in vlan_skb

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: <1207918405.22152.97.camel@ragnarok>
Date:	Fri, 11 Apr 2008 08:53:24 -0400
From:	Jeremy Jackson <jerj@...lanar.net>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Brian Oostenbrink <Brian_Oostenbrink@...-sierra.com>,
	linux-net@...r.kernel.org,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: Re-queueing of skb in vlan_skb_recv

On Fri, 2008-04-11 at 14:46 +0200, Patrick McHardy wrote:
> Brian Oostenbrink wrote:
> > In vlan_skb_recv, packets are generally stripped of their vlan header,
> > and then re-queued via netif_rx().  Is there a reason for re-queuing
> > these instead of calling netif_receive_skb() directly?  On our system
> > (an embedded linux router), this re-queuing has a significant
> > performance penalty.
> 
> Its done to save stack space. There's currently a discussion
> about making loopback use netif_receive_skb in case enough
> stack is still available. Once that patch gets merged I'll
> change VLAN in a similar way.

There was a patch floating around fixing VLAN + Bridge, I'm wondering if
it got any traction (ie merged), or if this would affect future merge of
that feature?


-- 
Jeremy Jackson
Coplanar Networks
(519)489-4903
http://www.coplanar.net
jerj@...lanar.net

--
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