From: Robert Olsson <Robert.Olsson@data.slu.se>
To: kuznet@ms2.inr.ac.ru
Cc: Robert.Olsson@data.slu.se (Robert Olsson),
dipankar@in.ibm.com, andrea@suse.de (Andrea Arcangeli),
davem@redhat.com (David S. Miller),
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
paulmck@us.ibm.com, akpm@osdl.org
Subject: Re: route cache DoS testing and softirqs
Date: Thu, 8 Apr 2004 16:07:31 +0200 [thread overview]
Message-ID: <16501.23715.401825.10935@robur.slu.se> (raw)
In-Reply-To: <200404081329.RAA16178@yakov.inr.ac.ru>
kuznet@ms2.inr.ac.ru writes:
> BTW what's about performance in this extremal situation?
First I used the patch to defer all softirq's to ksoftirq with call_rcu_bh()
patch. Sofar this has been the best combination giving both pure sofirq
performance and also good response from the userland apps.
I also tried other TCP apps netperf and could note any performance
degradation which I was expecting.
> Also, Robert, let's count the numbers again. With this change you should
> have latency much less 100msec when priority of ksoftirqd is high.
> So, rcu problem must be solved at current flow rates.
> This enforces me to suspect we have another source of overflows.
Certainly. I said to Dipankar we should not expect all overflows to disappear
the setup I use now. But the call_rcu_bh() patch improved things so it cured
some latency caused by RCU. But I don't think we can do much better now in
terms dst overflow.
> F.e. one silly place could be that you set gc_min_interval via sysctl,
I should not...
> which uses second resolution (yup :-(). With one second you get maximal
> ip_rt_max_size/1 second flow rate, it is _not_ a lot.
From /proc
gc_min_interval = 0
max_size = 262144
Cheers.
--ro
next prev parent reply other threads:[~2004-04-08 14:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 18:45 route cache DoS testing and softirqs Dipankar Sarma
2004-03-29 22:29 ` Andrea Arcangeli
2004-03-30 5:06 ` Srivatsa Vaddagiri
2004-03-30 5:35 ` Srivatsa Vaddagiri
2004-03-30 15:11 ` Andrea Arcangeli
2004-03-31 2:36 ` Rusty Russell
2004-03-30 14:43 ` Dipankar Sarma
2004-03-30 19:53 ` Dipankar Sarma
2004-03-30 20:47 ` Andrea Arcangeli
2004-03-30 21:06 ` Dipankar Sarma
2004-03-30 21:27 ` Andrea Arcangeli
2004-03-30 21:29 ` Robert Olsson
2004-03-31 7:36 ` Dipankar Sarma
2004-03-30 20:05 ` kuznet
2004-03-30 20:28 ` Dipankar Sarma
2004-04-01 6:00 ` kuznet
2004-03-30 21:14 ` Andrea Arcangeli
2004-03-30 21:30 ` David S. Miller
2004-03-30 21:37 ` Andrea Arcangeli
2004-03-30 22:22 ` David S. Miller
2004-03-30 22:49 ` Andrea Arcangeli
2004-03-31 20:46 ` Dipankar Sarma
2004-03-31 21:31 ` Andrea Arcangeli
2004-03-31 21:52 ` Dipankar Sarma
2004-03-30 22:33 ` Robert Olsson
2004-03-31 17:10 ` Dipankar Sarma
2004-03-31 18:46 ` Robert Olsson
2004-03-31 20:37 ` Dipankar Sarma
2004-03-31 21:28 ` Andrea Arcangeli
2004-03-31 21:43 ` Dipankar Sarma
2004-04-05 17:11 ` Robert Olsson
2004-04-05 21:22 ` Dipankar Sarma
2004-04-06 12:55 ` Robert Olsson
2004-04-06 19:52 ` Dipankar Sarma
2004-04-07 15:23 ` Robert Olsson
2004-04-07 19:48 ` Dipankar Sarma
2004-04-08 13:29 ` kuznet
2004-04-08 14:07 ` Robert Olsson [this message]
2004-03-31 22:36 ` Robert Olsson
2004-03-31 22:52 ` Andrea Arcangeli
2004-04-01 6:43 ` kuznet
2004-04-01 13:16 ` Andrea Arcangeli
2004-04-08 13:38 ` kuznet
2004-04-01 13:44 ` Robert Olsson
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=16501.23715.401825.10935@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=paulmck@us.ibm.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;
as well as URLs for NNTP newsgroup(s).