[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100208.153406.123254133.davem@davemloft.net>
Date: Mon, 08 Feb 2010 15:34:06 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: akpm@...ux-foundation.org
Cc: eric.dumazet@...il.com, pstaszewski@...are.pl,
netdev@...r.kernel.org
Subject: Re: [PATCH] dst: call cond_resched() in dst_gc_task()
From: Andrew Morton <akpm@...ux-foundation.org>
Date: Mon, 8 Feb 2010 15:26:06 -0800
> I assume that this function spends most of its time walking over busy
> entries? Is a more powerful data structure needed?
When you're getting pounded with millions of packets per second,
all mostly to different destinations (and thus resolving to
different routing cache entries), this is what happens.
For a busy router, really, this is normal behavior.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists