All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Justin Carlson <justinca@cs.cmu.edu>, linux-mips@oss.sgi.com
Subject: Re: __flush_cache_all() miscellany
Date: Wed, 29 May 2002 15:46:24 -0700	[thread overview]
Message-ID: <20020529154624.A2409@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1020529234323.17584P-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, May 29, 2002 at 11:46:58PM +0200

On Wed, May 29, 2002 at 11:46:58PM +0200, Maciej W. Rozycki wrote:

> > >  I converted a few flush_cache_all() invocations to __flush_cache_all() 
> > > where appropriate late last year, but the function is a bit older.  I
> > > think you might dig the linux-kernel list archives for a discussion on the
> > > semantics of flush_cache_all() (it's a nop for many MIPS CPUs) and
> > > friends.  The short description in Documentation/cachetlb.txt is a bit
> > > insufficient, I'm afraid. 
> > 
> > I don't like that function very much; it's sort of a shotgun approach
> > to flushing caches in a part of the kernel that's not too performance
> > relevant.  The whole interface sucks, should be replaced by something
> > more finegrained.
> 
>  Well, I suspect the API might be somewhat influenced by SPARC's oddities. 
> ;-) 

Historically that's certainly true.

As a general complaint about the style of interfaces of the cache stuff -
they're too low level.  Frequently we just don't know enough about the
situation to optimize the flush operation.

  Ralf

  reply	other threads:[~2002-05-29 22:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 16:50 __flush_cache_all() miscellany Justin Carlson
2002-05-29 19:26 ` Justin Carlson
2002-05-29 19:50   ` Maciej W. Rozycki
2002-05-29 20:20     ` Justin Carlson
2002-05-29 21:00       ` Maciej W. Rozycki
2002-05-29 21:33         ` Ralf Baechle
2002-05-29 21:46           ` Maciej W. Rozycki
2002-05-29 22:46             ` Ralf Baechle [this message]
2002-05-29 22:59         ` Justin Carlson
2002-05-29 23:24           ` Jun Sun
2002-06-03 17:23           ` Maciej W. Rozycki
2002-05-29 21:03   ` Kevin D. Kissell
2002-05-29 21:03     ` Kevin D. Kissell
2002-05-29 21:28     ` Ralf Baechle
2002-05-29 21:09   ` Ralf Baechle
2002-05-29 21:07 ` Ralf Baechle
2002-05-30 12:31   ` Florian Laws

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=20020529154624.A2409@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=justinca@cs.cmu.edu \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.