From: "Michael S. Zick" <mszick@morethan.org>
To: parisc-linux@lists.parisc-linux.org
Cc: Kyle McMartin <kyle@mcmartin.ca>,
John David Anglin <dave@hiauly1.hia.nrc.ca>
Subject: Re: [parisc-linux] Heavy Iron Reference Docs
Date: Sun, 30 Apr 2006 18:28:26 -0500 [thread overview]
Message-ID: <200604301828.26318.mszick@morethan.org> (raw)
In-Reply-To: <200604301801.23210.mszick@morethan.org>
On Sun April 30 2006 18:01, Michael S. Zick wrote:
>
> Scratches head...
>
> I wonder where Joel has his processors installed in relation to the
> two busses? Both on same buss or one per buss? Would his lockups
> go away if he picked the other relationship?
>
> I will ask him. (or perhaps I just did)
>
Browsing old parisc spinlock code, I find a comment that the N4K
can only have one outstanding PxTLB transaction at a time.
Is it not the PxTLB transactions that implement the inter-processor
coherency?
Which is of course required for inter-processor spinlocks to work.
And, of course, this being Linux, the queue is protected by a spinlock!
Did someone just shoot themselves in the foot?
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-04-30 23:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 3:50 [parisc-linux] Heavy Iron Reference Docs Michael S. Zick
2006-04-30 4:36 ` John David Anglin
2006-04-30 17:13 ` Kyle McMartin
2006-04-30 21:25 ` John David Anglin
2006-04-30 23:01 ` Michael S. Zick
2006-04-30 23:28 ` Michael S. Zick [this message]
2006-05-02 6:24 ` Grant Grundler
2006-05-02 11:27 ` Michael S. Zick
2006-04-30 23:30 ` John David Anglin
2006-05-01 3:23 ` Michael S. Zick
2006-05-02 6:00 ` Grant Grundler
2006-05-02 15:10 ` John David Anglin
2006-05-02 15:13 ` Kyle McMartin
2006-05-02 15:41 ` John David Anglin
2006-04-30 7:03 ` Grant Grundler
2006-04-30 13:12 ` Michael S. Zick
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=200604301828.26318.mszick@morethan.org \
--to=mszick@morethan.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=kyle@mcmartin.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/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