From: nisse@southpole.se (Niels Möller)
To: Cong Wang <cwang@twopensource.com>
Cc: netdev <netdev@vger.kernel.org>, Jonas Bonn <jonas@southpole.se>
Subject: Re: What's the right way to use a *large* number of source addresses?
Date: Mon, 26 May 2014 08:39:34 +0200 [thread overview]
Message-ID: <6zsinxt55l.fsf@southpole.se> (raw)
In-Reply-To: <CAHA+R7OkR_M9T51Y3zQa2QG3Rq1edJjT0SoMoaoD2tkyefnm4A@mail.gmail.com> (Cong Wang's message of "Fri, 23 May 2014 15:39:55 -0700")
Cong Wang <cwang@twopensource.com> writes:
> On Fri, May 23, 2014 at 2:38 AM, Niels Möller <nisse@southpole.se> wrote:
>>
>> So now I'm trying to figure out what's the Right Way to enable traffic
>> generations with a large number of source addresses, to possibly retire
>> the proprietary kernel module. I see a couple of different approaches:
>
> Isn't pktgen is what you are looking for?
No, I'd like to have a user-space application using a plain tcp socket
as the endpoint.
In my experience, pktgen is useful if you want to test the limits of raw
packet performance of network cards and drivers, or generate load on
networking equipment. But not for generating load on a real application,
where the data needs to follow some higher level protocol.
Regards,
/Niels
next prev parent reply other threads:[~2014-05-26 6:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 9:38 What's the right way to use a *large* number of source addresses? Niels Möller
2014-05-23 10:11 ` Florian Westphal
2014-05-23 10:49 ` Lukas Tribus
2014-05-23 12:26 ` Niels Möller
2014-05-23 14:12 ` Niels Möller
2014-05-23 12:53 ` sowmini varadhan
2014-05-23 14:14 ` Eric Dumazet
2014-05-24 12:06 ` Jamal Hadi Salim
2014-05-23 22:39 ` Cong Wang
2014-05-26 6:39 ` Niels Möller [this message]
2014-05-24 11:58 ` Jamal Hadi Salim
2014-05-24 14:44 ` Richard Weinberger
2014-05-24 15:13 ` Jamal Hadi Salim
2014-05-24 16:02 ` Richard Weinberger
2014-05-24 17:54 ` David Miller
2014-05-24 18:30 ` Jamal Hadi Salim
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=6zsinxt55l.fsf@southpole.se \
--to=nisse@southpole.se \
--cc=cwang@twopensource.com \
--cc=jonas@southpole.se \
--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).