From: Grant Grundler <grundler@cup.hp.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
Philipp.H.Rumpf@mathe.stud.uni-erlangen.de, mklein@dis.com,
sieler@allegro.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Progress - Update
Date: Wed, 01 Dec 1999 10:55:21 -0800 [thread overview]
Message-ID: <199912011856.KAA12102@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 01 Dec 1999 13:33:09 PST." <199912011833.NAA17015@hiauly1.hia.nrc.ca>
"John David Anglin" wrote:
...
> Also, we may need to flush the cache line for &var. The coding in buffer.c
> which caused the original panic in xchg looks dubiousin this regoard:
>
> /* Update the reuse list */
> tail->b_next_free = xchg(&reuse_list, NULL);
> reuse_list = bh;
If this data struct is only touched by processors, they are coherent
and flushing is not needed. (Except VM aliases...but I have to ignore
this case due to my ignorance). If any driver DMAs this data and the
platform is I/O coherent (ie has ccio, epic or sba driver), processor
doesn't need to flush either. Processor should only need to flush on
*any* (SMP or not) platform which is not I/O coherent (assume the page
is mapped cacheable).
grant
Grant Grundler
Unix Developement Lab
+1.408.447.7253
next prev parent reply other threads:[~1999-12-01 18:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-18 23:16 [parisc-linux] Progress John David Anglin
1999-11-19 3:30 ` Philipp Rumpf
1999-11-21 23:07 ` John David Anglin
1999-11-22 1:12 ` John David Anglin
1999-11-22 8:24 ` Philipp Rumpf
1999-11-22 9:59 ` Alan Cox
1999-11-22 15:54 ` Philipp Rumpf
1999-11-22 7:30 ` Philipp Rumpf
1999-11-22 18:11 ` John David Anglin
1999-11-22 18:27 ` Stan Sieler
1999-11-22 18:42 ` Philipp Rumpf
1999-11-22 18:33 ` Philipp Rumpf
1999-11-22 20:55 ` John David Anglin
1999-11-23 11:47 ` Philipp Rumpf
1999-11-23 16:19 ` John David Anglin
1999-11-23 18:03 ` Philipp Rumpf
1999-11-23 19:01 ` John David Anglin
1999-11-23 21:11 ` Stan Sieler
1999-11-24 10:00 ` Philipp Rumpf
1999-11-24 19:00 ` Stan Sieler
1999-11-24 19:33 ` Philipp Rumpf
1999-11-24 20:55 ` [parisc-linux] Progress - Update John David Anglin
1999-11-24 21:05 ` Philipp Rumpf
1999-11-24 21:27 ` Kirk Bresniker
1999-11-24 21:37 ` Philipp Rumpf
1999-11-24 22:38 ` Frank Rowand
1999-11-24 23:24 ` Cache Flushes Grant Grundler
1999-11-25 0:31 ` [parisc-linux] Progress - Update John David Anglin
1999-11-25 1:17 ` Alan Cox
1999-11-25 13:24 ` Philipp Rumpf
1999-11-25 23:47 ` John David Anglin
1999-11-30 18:17 ` John David Anglin
1999-11-30 18:21 ` Alan Cox
1999-11-30 18:32 ` Philipp Rumpf
1999-11-30 19:31 ` Alan Cox
1999-11-30 20:14 ` Mark Klein
1999-11-30 23:40 ` John David Anglin
1999-12-01 15:41 ` Philipp Rumpf
1999-12-01 18:03 ` Alan Cox
1999-12-01 18:29 ` Alex deVries
1999-12-01 18:34 ` Alan Cox
1999-12-02 2:51 ` Philipp Rumpf
1999-12-01 18:33 ` John David Anglin
1999-12-01 18:54 ` Alan Cox
1999-12-01 18:55 ` Grant Grundler [this message]
1999-11-26 13:40 ` Matthew Wilcox
1999-11-23 15:59 ` [parisc-linux] Progress Paul Bame
1999-11-23 16:33 ` John David Anglin
1999-11-23 17:05 ` Paul Bame
1999-11-23 20:15 ` John David Anglin
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=199912011856.KAA12102@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=Philipp.H.Rumpf@mathe.stud.uni-erlangen.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=mklein@dis.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=sieler@allegro.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