public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: VLAN egress performance
Date: Mon, 08 Feb 2010 17:58:57 +0100	[thread overview]
Message-ID: <87aavjfyum.fsf@isengard.friendlyfire.se> (raw)
In-Reply-To: <4B700DF5.1080406@trash.net> (Patrick McHardy's message of "Mon\, 08 Feb 2010 14\:13\:25 +0100")

Patrick McHardy <kaber@trash.net> writes:

>> Ingress VLAN  Egress VLAN  Packet Rate    CPU utilization (all cores)
>> No            No           5.0 Mpacket/s  ~70%
>> Yes           No           5.0 Mpacket/s  ~75%
>> No            Yes          1.4 Mpacket/s  ~26%
>> Yes           Yes          1.3 Mpacket/s  ~26%
>> 
> 2.6.32 contains VLAN multiqueue support and should scale better.

OK, excellent. I tried out 2.6.32.7 and it did 4.0 Mpacket/s with VLAN
on both ingress and egress, and ~4.7 Mpacket/s without any VLANs.

Thanks,
     Mattias

      parent reply	other threads:[~2010-02-08 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 12:24 VLAN egress performance Mattias Rönnblom
2010-02-08 13:13 ` Patrick McHardy
2010-02-08 13:24   ` Eric Dumazet
2010-02-08 16:58   ` Mattias Rönnblom [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=87aavjfyum.fsf@isengard.friendlyfire.se \
    --to=hofors@lysator.liu.se \
    --cc=kaber@trash.net \
    --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