[Top] [All Lists]

Re: Route cache performance under stress

To: hadi@xxxxxxxxxxxxxxxx
Subject: Re: Route cache performance under stress
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Mon, 09 Jun 2003 04:55:47 -0700 (PDT)
Cc: xerox@xxxxxxxxxx, sim@xxxxxxxxxxxxx, fw@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <20030609072227.R34462@xxxxxxxxxxxxxxxx>
References: <000401c32e5e$a707b6d0$4a00000a@badass> <20030609072227.R34462@xxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
   From: Jamal Hadi <hadi@xxxxxxxxxxxxxxxx>
   Date: Mon, 9 Jun 2003 07:38:44 -0400 (EDT)

   Yes, you have a nice setup and thats why you should test all the patches
   DaveM is posting. Dave, Paul is running in a real ISP environment i think
   he is very valuable in helping to test these patches and collect
   any says that might be needed. Now watch him disapear ;->
If he doesn't test my patches he isn't very useful,
so we'll see :-)

   Additional thought Dave: i think prefetching the rth would help in 2.5
   at least when you have lotsa collisions.
   call prefetch(nextrth) right after smp_read_barrier_depends() everywhere
   in route.c
You're going to prefetch "nextrth" when the first thing we're
going to access is "&nextrth->fl"? :-)

It only makes sense to prefetch the 'fl' member of the first hash
chain entry and that's what I've done in my tree.  This points out
that it would make sense to put the struct flowi up into the dst

<Prev in Thread] Current Thread [Next in Thread>