Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*net\/ipv4\/route\.c\s+GC\s+patch\:\s+is\s+this\s+insane\?\s*$/: 8 ]

Total 8 documents matching your query.

1. out (score: 1)
Author: xxxxxxxxxxxxxxxxxxxxx
Date: Mon, 31 May 2004 01:14:34 +1000
Hi guys, Attached is a patch to net/ipv4/route.c (against 2.4.23, sorry) to combat the 'dst cache full' issue. Essentially, there's a machine that I have access to (a router) that will report 'dst ca
/archives/netdev/2004-05/msg00471.html (8,828 bytes)

2. 64? (score: 1)
Author: xxxxxxxxx (Margit Schubert-While)
Date: Mon, 31 May 2004 14:21:02 +0200
Hello! If your traffic is sane and you got dst cache overflow you should probably try to reduce gc_min_interval so your GC can release a higher numbers of dst entries per second. Flushing active entr
/archives/netdev/2004-05/msg00503.html (9,033 bytes)

3. 3tL (score: 1)
Author: Robert.Olsson@xxxxxxxxxxx>
Date: Tue, 1 Jun 2004 00:08:01 +1000
This appears to already be the case, in 2.4.23's net/ipv4/route.c, at any rate. -- Daniel Stone <daniel@xxxxxxxxxxxxx> "The programs are documented fully by _The Rise and Fall of a Fooish Bar_, avail
/archives/netdev/2004-05/msg00506.html (9,268 bytes)

4. ne? (score: 1)
Author: one <daniel@xxxxxxxxxxxxx>
Date: Mon, 31 May 2004 17:06:00 +0200
OK! Well take a look at route stats /proc/net/rt_cache_stat (you can use rtstat app with a vmstat-like output) to ensure things are normal. If so you can try to decrease ip_rt_gc_min_interval further
/archives/netdev/2004-05/msg00507.html (8,770 bytes)

5. net/ipv4/route.c GC patch: is this insane? (score: 1)
Author: Daniel Stone <daniel@xxxxxxxxxxxxx>
Date: Mon, 31 May 2004 01:14:34 +1000
Hi guys, Attached is a patch to net/ipv4/route.c (against 2.4.23, sorry) to combat the 'dst cache full' issue. Essentially, there's a machine that I have access to (a router) that will report 'dst ca
/archives/netdev/2004-05/msg00989.html (8,828 bytes)

6. net/ipv4/route.c GC patch: is this insane? (score: 1)
Author: Robert Olsson <Robert.Olsson@xxxxxxxxxxx>
Date: Mon, 31 May 2004 14:21:02 +0200
Hello! If your traffic is sane and you got dst cache overflow you should probably try to reduce gc_min_interval so your GC can release a higher numbers of dst entries per second. Flushing active entr
/archives/netdev/2004-05/msg01021.html (9,093 bytes)

7. Re: net/ipv4/route.c GC patch: is this insane? (score: 1)
Author: Daniel Stone <daniel@xxxxxxxxxxxxx>
Date: Tue, 1 Jun 2004 00:08:01 +1000
This appears to already be the case, in 2.4.23's net/ipv4/route.c, at any rate. -- Daniel Stone <daniel@xxxxxxxxxxxxx> "The programs are documented fully by _The Rise and Fall of a Fooish Bar_, avail
/archives/netdev/2004-05/msg01024.html (9,425 bytes)

8. Re: net/ipv4/route.c GC patch: is this insane? (score: 1)
Author: Robert Olsson <Robert.Olsson@xxxxxxxxxxx>
Date: Mon, 31 May 2004 17:06:00 +0200
OK! Well take a look at route stats /proc/net/rt_cache_stat (you can use rtstat app with a vmstat-like output) to ensure things are normal. If so you can try to decrease ip_rt_gc_min_interval further
/archives/netdev/2004-05/msg01025.html (8,954 bytes)


This search system is powered by Namazu