| To: | Eric Dumazet <dada1@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [BUG] overflow in net/ipv4/route.c rt_check_expire() |
| From: | Robert Olsson <Robert.Olsson@xxxxxxxxxxx> |
| Date: | Fri, 1 Apr 2005 19:26:32 +0200 |
| Cc: | Robert Olsson <Robert.Olsson@xxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <424D780A.9000101@xxxxxxxxxxxxx> |
| References: | <42370997.6010302@xxxxxxxxxxxxx> <20050315103253.590c8bfc.davem@xxxxxxxxxxxxx> <42380EC6.60100@xxxxxxxxxxxxx> <20050316140915.0f6b9528.davem@xxxxxxxxxxxxx> <4239E00C.4080309@xxxxxxxxxxxxx> <20050331221352.13695124.davem@xxxxxxxxxxxxx> <424D5D34.4030800@xxxxxxxxxxxxx> <16973.28254.203492.400896@xxxxxxxxxxxx> <424D780A.9000101@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Eric Dumazet writes:
> According to oprofile, an unpatched kernel was spending more than 15% of
> time in route.c routines, now I see ip_route_input() at 1.88%
Would like to see absolute numbers for UP/SMP single flow and DoS to be
confident.
> I found it was better to adjust gc_interval to 1 (to let it fire every
> second and examine 1/300 table slots, or more if the dynamic behavior
> triggers), and ajust params so that rt_garbage_collect() doesnt run at all :
> rt_garbage_collect() can take forever to complete, blocking
> network trafic.
I don't think you can depend on timer for GC solely. Timer tick is
eternity for todays packet rates. You can distribute the GC load by allowing
it to run more frequent this in combination with huge cache seems to be a
very interesting approach given that you have memory.
--ro
|
| Previous by Date: | Re: RFC: Redirect-Device, Ben Greear |
|---|---|
| Next by Date: | Re: PATCH: IPSEC xfrm events, Masahide NAKAMURA |
| Previous by Thread: | Re: [BUG] overflow in net/ipv4/route.c rt_check_expire(), Eric Dumazet |
| Next by Thread: | Re: [BUG] overflow in net/ipv4/route.c rt_check_expire(), David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |