mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][ANNOUNCE] Linux 2.5.68-ce2
Date: Tue, 22 Apr 2003 16:12:05 -0400	[thread overview]
Message-ID: <200304221614_MC3-1-3589-7E0C@compuserve.com> (raw)

Zwane Mwaikambo wrote:

.> What benefit did you see from that, what was your reasoning behind the 
.> change? Have you noted 16byte code alignment improvements with some processors?

 I posted a message about that a while ago after noticing that some
interrupt handlers started in the last 4 bytes of a(n assumed) 16-byte
cacheline, and the first instruction in all of them was 5 bytes long.
According to the manuals the penalties for this can be huge, and there's
no way to mitigate them with branch prediction and prefetch.  (How do you
predict an interrupt?)  And even if you hit L1 with both fetches there is
a small penalty...

 I couldn't find any way to test the patch, but there doesn't seem to be
any downside other than a lost 1K of memory on IOAPIC machines, and a possible
larger working set fighting for L1 space but that would require heavy
concurrent use of a very large number of interrupt vectors.


-------
 Chuck

             reply	other threads:[~2003-04-22 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:12 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-22 23:34 Chuck Ebbert
2003-04-22 20:29 Chuck Ebbert
2003-04-22 18:26 Chuck Ebbert
2003-04-22 19:57 ` Jörn Engel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304221614_MC3-1-3589-7E0C@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®