From: Ben Greear <greearb@candelatech.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: 802.1q HW filter spammage in 3.7.2+ kernels.
Date: Wed, 16 Jan 2013 06:03:04 -0800 [thread overview]
Message-ID: <50F6B318.2010707@candelatech.com> (raw)
In-Reply-To: <1358316108.19956.82.camel@edumazet-glaptop>
On 01/15/2013 10:01 PM, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> On Tue, 2013-01-15 at 17:36 -0800, Ben Greear wrote:
>> My kernel logs are full of this (I have 2000 macvlans).
>
> Are you using 2000 macvlans on the same device ? Interesting...
Well, in this case, we have 1000 mac-vlans on each of 2 1G
Ethernet ports, but 2000 on a single device has been used
as well.
>
> I am wondering how multicast/broadcast messages don't generate a huge
> load and packet drops, since we clone packets for every macvlan, and
> queue then to netif_rx()
>
I have added ARP patches to do a random retry timer to help spread
out the ARP requests a bit, at least. The system is still sluggish
at times, but it does function. With a fixed-interval ARP timer, things
can get into very bad patterns.
http://patchwork.ozlabs.org/patch/9301/
My test cases often require SO_BINDTODEVICE to function with full features,
with one traffic-application per interface, so mac-vlans seems the easiest
way to scale.
> I guess you dont use IPv6 on these macvlans ?
I have...but many use cases use far fewer (virtual) interfaces.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-01-16 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 1:36 802.1q HW filter spammage in 3.7.2+ kernels Ben Greear
2013-01-16 6:01 ` Eric Dumazet
2013-01-16 6:11 ` David Miller
2013-01-17 21:30 ` [PATCH] macvlan: fix macvlan_get_size() Eric Dumazet
2013-01-17 21:41 ` David Miller
2013-01-16 14:03 ` Ben Greear [this message]
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=50F6B318.2010707@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).