From: Benjamin Herrenschmidt <bh40@calva.net>
To: Giuliano Pochini <pochini@denise.shiny.it>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: progress on l2cr
Date: Sat, 22 Jul 2000 22:13:20 +0200 [thread overview]
Message-ID: <20000722201320.21455@192.168.1.10> (raw)
In-Reply-To: <3978FB1C.388059D1@denise.shiny.it>
>
>Is there any reason to keep the L2 cache data-only ?
There are some rare cases where it can be useful, yes. Like when flushing
it, to avoid the flush code to pollute it.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-22 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 22:26 progress on l2cr Guillaume Laurès
2000-07-18 6:54 ` Guillaume Laurès
2000-07-18 8:03 ` Benjamin Herrenschmidt
2000-07-22 1:38 ` Giuliano Pochini
2000-07-22 20:13 ` Benjamin Herrenschmidt [this message]
2000-08-01 0:18 ` Giuliano Pochini
2000-07-31 18:42 ` Benjamin Herrenschmidt
2000-08-06 3:25 ` Giuliano Pochini
2000-08-06 9:33 ` Timothy A. Seufert
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=20000722201320.21455@192.168.1.10 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@denise.shiny.it \
/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).