From: "David S. Miller" <davem@davemloft.net>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: gnb@sgi.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
jeremy@sgi.com, johnip@sgi.com, netdev@oss.sgi.com
Subject: Re: [PATCH] I/O space write barrier
Date: Wed, 29 Sep 2004 13:50:29 -0700 [thread overview]
Message-ID: <20040929135029.38444afd.davem@davemloft.net> (raw)
In-Reply-To: <200409291343.55863.jbarnes@engr.sgi.com>
On Wed, 29 Sep 2004 13:43:55 -0700
Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> The patch that actually implements mmiowb() already does this, I think Greg
> just used his patch for testing. The proper way to do it of course is to
> just use mmiowb() where needed in tg3 after the write barrier patch gets in.
Perfect, please send me a tg3 patch once the mmiowb() bits
go into the tree.
Thanks a lot.
next prev parent reply other threads:[~2004-09-29 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409271103.39913.jbarnes@engr.sgi.com>
2004-09-29 10:36 ` [PATCH] I/O space write barrier Greg Banks
2004-09-29 20:35 ` David S. Miller
2004-09-29 20:43 ` Jesse Barnes
2004-09-29 20:50 ` David S. Miller [this message]
2004-09-30 2:23 ` Greg Banks
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=20040929135029.38444afd.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=gnb@sgi.com \
--cc=jbarnes@engr.sgi.com \
--cc=jeremy@sgi.com \
--cc=johnip@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).