From: Benny Amorsen <benny+usenet@amorsen.dk>
To: "Martín Ferrari" <martin.ferrari@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
Mathieu Lacage <mathieu.lacage@sophia.inria.fr>
Subject: Re: Performance problem in network namespaces
Date: Tue, 04 May 2010 11:48:11 +0200 [thread overview]
Message-ID: <m3y6g0m204.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <q2tb9800b71005030225q21365e3ch8dd5b35383a32e8a@mail.gmail.com> ("Martín Ferrari"'s message of "Mon, 3 May 2010 11:25:20 +0200")
Martín Ferrari <martin.ferrari@gmail.com> writes:
> 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...)
/Benny
next prev parent reply other threads:[~2010-05-04 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 9:25 Performance problem in network namespaces Martín Ferrari
2010-05-04 9:48 ` Benny Amorsen [this message]
2010-05-05 7:37 ` Martín Ferrari
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=m3y6g0m204.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=martin.ferrari@gmail.com \
--cc=mathieu.lacage@sophia.inria.fr \
--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