[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 5 May 2010 09:37:06 +0200
From: Martín Ferrari <martin.ferrari@...il.com>
To: Benny Amorsen <benny+usenet@...rsen.dk>
Cc: netdev <netdev@...r.kernel.org>,
Mathieu Lacage <mathieu.lacage@...hia.inria.fr>
Subject: Re: Performance problem in network namespaces
Hi Benny,
On Tue, May 4, 2010 at 11:48, Benny Amorsen <benny+usenet@...rsen.dk> wrote:
>> When running some benchmarks to test the feasibility of using
>> namespaces for emulating networks, I have found a big drop in
>> performance when one of the namespaces is performing routing of
>> packets.
> Is this problem specific to vnet, or do the other types of interfaces
> suffer from it as well? (phys, vlan, macvlan...)
Seems that it is specific to vnet, but if there's other way of having
datagrams created locally that get into the routing code before
leaving the system, maybe that would have the same problem.
I tried a couple of combinations that somehow included routing in the mix:
- routing loop over the same ethernet device (e1000e)
- routing between eth and wlan (iwlagn)
- eth and veth (with the paired veth inside a different namespace)
- wlan and veth (ditto)
In all those cases, I see that in ip_forward() the headroom is already
enough, and I think is due to the fact that the hardware drivers use
netdev_alloc_skb which already adds NET_SKB_PAD to the length
requested.
Using macvlan over the real devices showed the same results.
I also tried:
- eth and wlan: packets arriving from eth had a headroom of 48, but
80 was needed to pass it to wlan
--
Martín Ferrari
--
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