linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Gabriel Paubert <paubert@iram.es>,
	paulus@linuxcare.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Patch for optimize context switch
Date: Tue, 22 Feb 2000 11:50:01 +0100	[thread overview]
Message-ID: <20000222115001.027256@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.HPX.4.10.10002221001530.4957-100000@gra-ux1.iram.es>


On Tue, Feb 22, 2000, Gabriel Paubert <paubert@iram.es> wrote:

>Exactly, context switches are infrequent and should be benchmarked at
>least after having invalidated the code from the instruction cache
>(whether it should also be pushed out of the L2 cache is more questionable
>but I would also push it out since L2 cache is only direct mapped or 2 way
>set associative on most processors). Besides the time of the loop is
>dominated by the execution synchronized mtsrin. Actually the only
>processor on which it might be a clear win is the 601.

BTW. There's an idea that have been idling in my mind for some time:

Do you think there would be any interest into adding code to some drivers
for invalidating the data cache of buffers before doing DMA-read i/os to
them ? (For example invalidating the block buffers before or just after
having started a DMA read in the IDE driver).

Those datas will be replaced by new datas, so invalidating them before
(or at the beginning of) the transfer will help avoiding snooping hits
during the transfer itself, and eventually help keeping more useful
things in the cache.

I'm not sure this would have any measurable impact, I may just setup a
lmbench and try it out once I'm finished with my current stuffs.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-22 10:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-21 10:49 Patch for optimize context switch FASSINO Jean-Philippe
2000-02-21 23:12 ` Paul Mackerras
2000-02-22  9:27   ` Gabriel Paubert
2000-02-22 10:50     ` Benjamin Herrenschmidt [this message]
2000-02-22 11:13       ` Gabriel Paubert
2000-02-22  9:30   ` FASSINO Jean-Philippe
2000-02-22 11:23     ` FASSINO Jean-Philippe
2000-02-22 11:33       ` FASSINO Jean-Philippe
2000-02-22 11:50         ` Gabriel Paubert
2000-02-22 11:40     ` Gabriel Paubert

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=20000222115001.027256@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    --cc=paulus@linuxcare.com \
    /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;
as well as URLs for NNTP newsgroup(s).