From: "Jeremy M. Guthrie" <jeremy.guthrie@berbee.com>
To: netdev@oss.sgi.com
Cc: Robert Olsson <Robert.Olsson@data.slu.se>
Subject: Re: V2.4 policy router operates faster/better than V2.6
Date: Sun, 16 Jan 2005 10:22:27 -0600 [thread overview]
Message-ID: <200501161022.30600.jeremy.guthrie@berbee.com> (raw)
In-Reply-To: <16874.24305.461492.48668@robur.slu.se>
[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]
On Sunday 16 January 2005 06:32 am, Robert Olsson wrote:
> Jeremy M. Guthrie writes:
> > I actually upped the buffer count to 8192 buffers instead of 10k.
> > Of the 74 samples I have thus far, 57 have been clean of errors.
> > Most of the sample errors appear to be shortly after the cache flush.
>
> I don't really believe in increasing RX buffers to this extent. We
> verified that you have CPU available and the drops occur when the timer
> based GC happens. Increasing buffers decreases overall performance and adds
> jitter.
I just took a look at my logs, the increase to the max on the card of 4K RX
buffers has stopped packet drops except during GC. I agree, it isn't pretty
and it is not the solution I would like. In the mean time, it has at least
stopped the 0.3% round-the-clock packet loss which I was seeing even at rates
as low as 25K pps.
> We saw also the timed based GC were taking the dst-entries from about
> 600k to 40k in one shot. I think this what we should look into. Just
> GC is "work" also after GC a lot flows has to be recreated doing fib
> lookup and creating new entries. We want to smoothen the GC process so
> happen more frequent and does less work.
Agreed. I went to the extreme because I can really see the % idle CPU. If I
am constantly setting up new flows then the % of free CPU shoots way down.
Minus the effects of GC, a larger flow table equates into free CPU.
> Some time ago an "in-flow" GC (as opposed to timer based) was added to
> the routing code look for cand in route.c. In setup like yours (and ours)
> it would be better to relay on this process to a higher extent. Anyway
> in /proc/sys/net/ipv4/route/ you have the files.
> gc_elasticity, gc_interval, gc_thresh etc I would avoid gc_min_interval.
> And you can play with your running system and for drops without causing
> your users to much pain.
> We save the patch for routing without route hash and GC until later,
Okay. I will bring my interval down from an hour down to ten minutes and do
further tuning.
--
--------------------------------------------------
Jeremy M. Guthrie jeremy.guthrie@berbee.com
Senior Network Engineer Phone: 608-298-1061
Berbee Fax: 608-288-3007
5520 Research Park Drive NOC: 608-298-1102
Madison, WI 53711
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-16 16:22 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 20:55 V2.4 policy router operates faster/better than V2.6 Jeremy M. Guthrie
2005-01-03 22:51 ` Stephen Hemminger
2005-01-03 22:56 ` Jeremy M. Guthrie
2005-01-05 13:18 ` Robert Olsson
2005-01-05 15:18 ` Jeremy M. Guthrie
2005-01-05 16:30 ` Robert Olsson
2005-01-05 17:35 ` Jeremy M. Guthrie
2005-01-05 19:25 ` Jeremy M. Guthrie
2005-01-05 20:22 ` Robert Olsson
2005-01-05 20:52 ` Jeremy M. Guthrie
2005-01-06 15:26 ` Jeremy M. Guthrie
2005-01-06 18:15 ` Robert Olsson
2005-01-06 19:35 ` Jeremy M. Guthrie
2005-01-06 20:29 ` Robert Olsson
2005-01-06 20:54 ` Jeremy M. Guthrie
2005-01-06 20:55 ` Jeremy M. Guthrie
2005-01-06 21:19 ` Jeremy M. Guthrie
2005-01-06 21:36 ` Robert Olsson
2005-01-06 21:46 ` Jeremy M. Guthrie
2005-01-06 22:11 ` Robert Olsson
2005-01-06 22:18 ` Jeremy M. Guthrie
2005-01-06 22:35 ` Robert Olsson
2005-01-07 16:17 ` Jeremy M. Guthrie
2005-01-07 19:18 ` Robert Olsson
2005-01-07 19:38 ` Jeremy M. Guthrie
2005-01-07 20:07 ` Robert Olsson
2005-01-07 20:14 ` Jeremy M. Guthrie
2005-01-07 20:40 ` Robert Olsson
2005-01-07 21:06 ` Jeremy M. Guthrie
2005-01-07 21:30 ` Robert Olsson
2005-01-11 15:11 ` Jeremy M. Guthrie
2005-01-07 22:28 ` Jesse Brandeburg
2005-01-07 22:50 ` Jeremy M. Guthrie
2005-01-07 22:57 ` Stephen Hemminger
2005-01-11 15:17 ` Jeremy M. Guthrie
2005-01-11 16:40 ` Robert Olsson
2005-01-12 1:27 ` Jeremy M. Guthrie
2005-01-12 15:11 ` Robert Olsson
2005-01-12 16:24 ` Jeremy M. Guthrie
2005-01-12 19:27 ` Robert Olsson
2005-01-12 20:11 ` Jeremy M. Guthrie
2005-01-12 20:21 ` Robert Olsson
2005-01-12 20:30 ` Jeremy M. Guthrie
2005-01-12 20:45 ` Jeremy M. Guthrie
2005-01-12 22:02 ` Robert Olsson
2005-01-12 22:21 ` Jeremy M. Guthrie
[not found] ` <16869.42247.126428.508479@robur.slu.se>
2005-01-12 22:42 ` Jeremy M. Guthrie
2005-01-12 22:47 ` Jeremy M. Guthrie
2005-01-12 23:19 ` Robert Olsson
2005-01-12 23:23 ` Jeremy M. Guthrie
2005-01-13 8:56 ` Robert Olsson
2005-01-13 19:28 ` Jeremy M. Guthrie
2005-01-13 20:00 ` David S. Miller
2005-01-13 20:43 ` Jeremy M. Guthrie
2005-01-13 23:13 ` David S. Miller
2005-01-13 21:12 ` Robert Olsson
2005-01-13 22:27 ` Jeremy M. Guthrie
2005-01-14 15:44 ` Robert Olsson
2005-01-14 14:59 ` Jeremy M. Guthrie
2005-01-14 16:05 ` Robert Olsson
2005-01-14 19:00 ` Jeremy M. Guthrie
2005-01-14 19:26 ` Jeremy M. Guthrie
2005-01-16 12:32 ` Robert Olsson
2005-01-16 16:22 ` Jeremy M. Guthrie [this message]
2005-01-19 15:03 ` Jeremy M. Guthrie
2005-01-19 22:18 ` Robert Olsson
2005-01-20 1:50 ` Jeremy M. Guthrie
2005-01-20 11:30 ` Robert Olsson
2005-01-20 14:37 ` Jeremy M. Guthrie
2005-01-20 17:01 ` Robert Olsson
2005-01-20 17:14 ` Jeremy M. Guthrie
2005-01-20 21:53 ` Robert Olsson
2005-01-21 21:20 ` Jeremy M. Guthrie
2005-01-21 15:23 ` Robert Olsson
2005-01-21 21:24 ` Jeremy M. Guthrie
2005-01-31 15:37 ` Jeremy M. Guthrie
2005-01-31 18:06 ` Robert Olsson
2005-01-12 22:05 ` Jeremy M. Guthrie
2005-01-12 22:22 ` Robert Olsson
2005-01-12 22:30 ` Jeremy M. Guthrie
2005-01-11 17:17 ` Jeremy M. Guthrie
2005-01-11 18:46 ` Robert Olsson
2005-01-12 1:30 ` Jeremy M. Guthrie
2005-01-12 16:02 ` Robert Olsson
2005-01-04 15:07 ` Jeremy M. Guthrie
[not found] <200501071619.54566.jeremy.guthrie@berbee.com>
2005-01-07 23:23 ` Jesse Brandeburg
2005-01-10 21:11 ` Jeremy M. Guthrie
[not found] <C925F8B43D79CC49ACD0601FB68FF50C02D39006@orsmsx408>
2005-01-13 22:55 ` Jeremy M. Guthrie
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=200501161022.30600.jeremy.guthrie@berbee.com \
--to=jeremy.guthrie@berbee.com \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@oss.sgi.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).