| To: | ak@xxxxxxx |
|---|---|
| Subject: | Re: Route cache performance under stress |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 09 Jun 2003 03:13:41 -0700 (PDT) |
| Cc: | sim@xxxxxxxxxxxxx, xerox@xxxxxxxxxx, fw@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, kuznet@xxxxxxxxxxxxx, Robert.Olsson@xxxxxxxxxxx |
| In-reply-to: | <20030609101302.GA9643@xxxxxxxxxxxxx> |
| References: | <20030609094734.GD2728@xxxxxxxxxxxxx> <20030609.030334.02284330.davem@xxxxxxxxxx> <20030609101302.GA9643@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Andi Kleen <ak@xxxxxxx> Date: Mon, 9 Jun 2003 12:13:02 +0200 On Mon, Jun 09, 2003 at 03:03:34AM -0700, David S. Miller wrote: > True, but the real bug is that we're initializing any of this > crap here at all. Right now we write over the same cachelines > 3 or so times. It should really just happen once. It's unlikely to be the reason for the profile hit on a modern x86. They are all really fast at reading/writing L1. It's store buffer compression that's being messed up. I've seen this on just about any processor. This is also why the net/core/skbuff.c initialization hacks are so effective as well. Trust me, this has every symptom of excess store buffer traffic :) |
| Previous by Date: | Re: Route cache performance under stress, Andi Kleen |
|---|---|
| Next by Date: | Re: Route cache performance under stress, YOSHIFUJI Hideaki / 吉藤英明 |
| Previous by Thread: | Re: Route cache performance under stress, Andi Kleen |
| Next by Thread: | Re: Route cache performance under stress, YOSHIFUJI Hideaki / 吉藤英明 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |