From: Daniel Lezcano <daniel.lezcano@free•fr>
To: Andrian Nord <nightnord@gmail•com>
Cc: lxc-users@lists•sourceforge.net,
Patrick McHardy <kaber@trash•net>,
Linux Netdev List <netdev@vger•kernel.org>,
Eric Dumazet <eric.dumazet@gmail•com>
Subject: Re: [Lxc-users] Bad checksums and lost packets with macvlan on dummy
Date: Sun, 27 Feb 2011 16:14:39 +0100 [thread overview]
Message-ID: <4D6A6A5F.4030707@free.fr> (raw)
In-Reply-To: <20110223170512.GA10277@nord.niifaq.ru>
On 02/23/2011 06:13 PM, Andrian Nord wrote:
> On Mon, Feb 21, 2011 at 05:07:31PM +0100, Daniel Lezcano wrote:
>> I Cc'ed the netdev mailing list and Patrick in case my analysis is wrong
>> or incomplete.
> I'm confirming, that this happens only when macvlan's are onto dummy net
> device. In case of some physical interface under macvlan there is no lost
> packages and no broken checksums.
I did some tests with a 2.6.35 kernel version and it seems the checksum
errors do not appear.
I noticed there are some changes in the dummy setup function:
dev->features |= NETIF_F_SG | NETIF_F_FRAGLIST | NETIF_F_TSO;
dev->features |= NETIF_F_NO_CSUM | NETIF_F_HIGHDMA | NETIF_F_LLTX;
May be that was introduced by commit:
commit 6d81f41c58c69ddde497e9e640ba5805aa26e78c
Author: Eric Dumazet <eric.dumazet@gmail•com>
Date: Mon Sep 27 20:50:33 2010 +0000
dummy: percpu stats and lockless xmit
Converts dummy network device driver to :
- percpu stats
- 64bit stats
- lockless xmit (NETIF_F_LLTX)
- performance features added (NETIF_F_SG | NETIF_F_FRAGLIST |
NETIF_F_TSO | NETIF_F_NO_CSUM | NETIF_F_HIGHDMA)
Signed-off-by: Eric Dumazet <eric.dumazet@gmail•com>
Signed-off-by: David S. Miller <davem@davemloft•net>
Eric,
Andrian is observing, with a couple of macvlan (in bridge mode) on top
of a dummy interface, a lot of checksums error and packets drop.
Each macvlan is in a different network namespace and the dummy interface
is in the init_net.
Any ideas ?
next prev parent reply other threads:[~2011-02-27 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110221150710.GA5651@nord.niifaq.ru>
[not found] ` <4D6282DB.2080204@free.fr>
[not found] ` <20110221153421.GA6602@nord.niifaq.ru>
2011-02-21 16:07 ` [Lxc-users] Huge ammount of invalid checksum packets on macvlan Daniel Lezcano
[not found] ` <4D628DC3.9000400-GANU6spQydw@public.gmane.org>
2011-02-21 17:39 ` Andrian Nord
2011-02-23 17:13 ` [Lxc-users] Bad checksums and lost packets with macvlan on dummy Andrian Nord
2011-02-24 10:20 ` Daniel Lezcano
2011-02-26 20:38 ` Andrian Nord
2011-02-27 15:14 ` Daniel Lezcano [this message]
2011-02-27 19:50 ` Eric Dumazet
2011-02-27 20:35 ` Daniel Lezcano
2011-02-28 7:45 ` [Lxc-users] " Eric Dumazet
2011-03-01 13:29 ` Daniel Lezcano
2011-03-01 16:51 ` Patrick McHardy
2011-03-01 20:04 ` Daniel Lezcano
2011-03-02 11:03 ` Patrick McHardy
2011-03-02 16:03 ` Daniel Lezcano
2011-03-02 18:03 ` Patrick McHardy
2011-03-02 18:33 ` Daniel Lezcano
2011-03-03 14:30 ` Changli Gao
2011-03-08 14:41 ` Patrick McHardy
[not found] ` <4D764030.8020202-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
2011-03-12 21:59 ` Daniel Lezcano
2011-03-12 22:07 ` [Lxc-users] " Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6A6A5F.4030707@free.fr \
--to=daniel.lezcano@free$(echo .)fr \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=kaber@trash$(echo .)net \
--cc=lxc-users@lists$(echo .)sourceforge.net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nightnord@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox