From: Eric Dumazet <eric.dumazet@gmail.com>
To: sedat.dilek@gmail.com
Cc: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] softirq: reduce latencies
Date: Thu, 03 Jan 2013 05:31:59 -0800 [thread overview]
Message-ID: <1357219919.21409.24519.camel@edumazet-glaptop> (raw)
In-Reply-To: <CA+icZUVEvzyrPsQG1QWLnHxhtaewaWTOVzBpTnLqjKuHMjjFHg@mail.gmail.com>
On Thu, 2013-01-03 at 14:12 +0100, Sedat Dilek wrote:
> Hi Eric,
>
> your patch from [2] applies cleanly on top of Linux v3.8-rc2.
> I would like to test it.
> In [1] you were talking about benchmarks you did.
> Can you describe them or provide a testcase (script etc.)?
> You made only network testing?
Yes I did network testing :
- net_rx_action() softirq handler is the typical function that can
consume 2 ms per call.
I did some netperf sessions, with multiqueue 10G nics, tuned to that IRQ
would be handled by few cpus.
(check /proc/irq/*/eth0-$QUEUE/../smp_affinity )
Another way to make the softirq processing use more cpu cycles is by
adding a fake iptable setup like :
for n in `seq 1 100`
do
iptables -I INPUT
done
A common network load is to launch ~200 concurrent TCP_RR netperf
sessions like the following
netperf -H remote_host -t TCP_RR -l 1000
And then you can launch some netperf asking P99_LATENCY results :
netperf -H remote_host -t TCP_RR -- -k P99_LATENCY
You can play with taskset or netperf option -T to force
netperf/netserver running on given cpus.
next prev parent reply other threads:[~2013-01-03 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 13:12 [PATCH net-next] softirq: reduce latencies Sedat Dilek
2013-01-03 13:31 ` Eric Dumazet [this message]
2013-01-03 19:41 ` Rick Jones
2013-01-04 4:41 ` Eric Dumazet
2013-01-04 5:31 ` Sedat Dilek
2013-01-04 6:54 ` Eric Dumazet
2013-01-04 11:57 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2013-01-03 12:28 Eric Dumazet
2013-01-03 20:46 ` Andrew Morton
2013-01-03 22:41 ` Eric Dumazet
2013-01-04 5:16 ` Namhyung Kim
2013-01-04 6:53 ` Eric Dumazet
[not found] ` <787701357283699@web24e.yandex.ru>
2013-01-04 7:46 ` Eric Dumazet
2013-01-03 22:08 ` Ben Hutchings
2013-01-03 22:40 ` Eric Dumazet
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=1357219919.21409.24519.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
/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