From: Or Gerlitz <ogerlitz@voltaire.com>
To: Ben Greear <greearb@candelatech.com>
Cc: netdev@vger.kernel.org
Subject: Re: some veth related issues
Date: Wed, 05 Aug 2009 07:40:04 +0300 [thread overview]
Message-ID: <4A790D24.9000008@voltaire.com> (raw)
In-Reply-To: <4A785824.2030500@candelatech.com>
Ben Greear wrote:
> Try setting clone to 0. Might be that sending cloned pkts over veth is
> a bad idea.
okay, thanks, this fixed the problem, however it seems there's some
performance loss, with cloning I saw numbers of 500K packets-per-second
and above where without cloning I get about 400K PPS.
Or.
next prev parent reply other threads:[~2009-08-05 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 14:30 some veth related issues Or Gerlitz
2009-08-04 15:47 ` Ben Greear
2009-08-05 4:40 ` Or Gerlitz [this message]
2009-08-05 4:48 ` Ben Greear
2009-08-05 5:41 ` bridge vs macvlan performance (was: some veth related issues) Or Gerlitz
2009-08-05 5:50 ` bridge vs macvlan performance Ben Greear
2009-08-05 7:02 ` Or Gerlitz
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=4A790D24.9000008@voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=greearb@candelatech.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).