From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] mmio barrier patch update
Date: Thu, 10 Jan 2002 21:28:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805800@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805779@msgid-missing>
On Thu, Jan 10, 2002 at 01:28:35PM -0800, David Mosberger wrote:
> I kind of doubt a loop of reads would yield acceptable performance,
> but it is a solution that should work properly, so I'm OK with it. I
> applied your patch to the 2.5 tree for now.
You're right that it would probably be slow, but I'm hoping that most
platforms have a sane way to address this problem. I know, for
example, that the mips64 port can use a simple 'sync' instruction to
accomplish the same thing. Thanks for applying the patch. Any ideas
on how I might go about getting this macro accepted by other platform
maintainers so that we can sprinkle it into drivers as necessary?
Thanks,
Jesse
prev parent reply other threads:[~2002-01-10 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 1:36 [Linux-ia64] [PATCH] mmio barrier patch update Jesse Barnes
2002-01-10 21:28 ` Jesse Barnes [this message]
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=marc-linux-ia64-105590698805800@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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