| To: | hadi@xxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Route cache performance under stress |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 09 Jun 2003 05:32:18 -0700 (PDT) |
| Cc: | xerox@xxxxxxxxxx, sim@xxxxxxxxxxxxx, fw@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx |
| In-reply-to: | <20030609080430.I34540@shell.cyberus.ca> |
| References: | <20030609072227.R34462@shell.cyberus.ca> <20030609.045547.91327851.davem@redhat.com> <20030609080430.I34540@shell.cyberus.ca> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Jamal Hadi <hadi@xxxxxxxxxxxxxxxx> Date: Mon, 9 Jun 2003 08:18:50 -0400 (EDT) I found in my tests with a ethernet driver that prefetching the _next_ dma descriptor gave better numbers than prefetching the current one but i didnt spend too much time. Two issues: 1) We have some cycles to borrow for head entry, we can make prefetch right before rcu_read_lock() 2) Ideally, hash chains will not exceed 1 (2 at the max) entries. Just some thinking... |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Route cache performance under stress, Jamal Hadi |
|---|---|
| Next by Date: | Re: [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6, Masahide NAKAMURA |
| Previous by Thread: | Re: Route cache performance under stress, Jamal Hadi |
| Next by Thread: | Re: Route cache performance under stress, Jamal Hadi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |