From: Andrea Arcangeli <andrea@suse.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Geert Uytterhoeven <geert@linux-m68k.org>,
James Simmons <jsimmons@linux-fbdev.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: fbcon slowness [was NTP on 2.4.2?]
Date: Fri, 6 Apr 2001 20:34:40 +0200 [thread overview]
Message-ID: <20010406203440.O28118@athlon.random> (raw)
In-Reply-To: <m13dbmw4he.fsf@frodo.biederman.org> <Pine.GSO.3.96.1010406191454.15958I-100000@delta.ds2.pg.gda.pl>
In-Reply-To: <Pine.GSO.3.96.1010406191454.15958I-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Fri, Apr 06, 2001 at 07:27:24PM +0200
On Fri, Apr 06, 2001 at 07:27:24PM +0200, Maciej W. Rozycki wrote:
> [..] You normally have
> non-cached locations buffered (since you don't always need peripheral
> device accesses to be posted immediately) and can force a writeback with a
> memory barrier. [..]
ev6 works the way you described AFIK (to flush the write buffer you can use
wmb(), note that wmb() semantics doesn't require the cpu to really "flush" but
just to keep writes oredered across other mb or wmb, but it's basically the
same from a software point of you and flushing the write buffer synchronously
obviously provides that semantics). I didn't followed very closely the
previous part of the thread so I'm not sure what is the issue.
Andrea
next prev parent reply other threads:[~2001-04-06 18:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 3:04 [Linux-fbdev-devel] Re: fbcon slowness [was NTP on 2.4.2?] James Simmons
2001-04-05 12:03 ` Eric W. Biederman
2001-04-05 12:12 ` Geert Uytterhoeven
2001-04-05 13:15 ` Maciej W. Rozycki
2001-04-05 18:20 ` Eric W. Biederman
2001-04-06 10:09 ` Ivan Kokshaysky
2001-04-06 13:19 ` Eric W. Biederman
2001-04-06 17:27 ` Maciej W. Rozycki
2001-04-06 18:34 ` Andrea Arcangeli [this message]
2001-04-06 19:31 ` Maciej W. Rozycki
2001-04-06 17:13 ` Maciej W. Rozycki
2001-04-08 18:11 ` Ivan Kokshaysky
2001-04-09 10:02 ` Maciej W. Rozycki
2001-04-09 11:05 ` Ivan Kokshaysky
2001-04-06 17:07 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-04-03 2:04 James Simmons
2001-04-01 14:54 James Simmons
2001-04-01 21:35 ` Jamie Lokier
2001-03-31 4:15 James Simmons
2001-03-31 4:11 James Simmons
2001-04-02 22:44 ` Alan Cox
2001-04-03 6:23 ` Geert Uytterhoeven
2001-04-03 12:21 ` Alan Cox
2001-04-04 7:50 ` Eric W. Biederman
2001-04-04 8:47 ` Jamie Lokier
2001-03-31 3:47 James Simmons
2001-03-31 14:15 ` Jamie Lokier
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=20010406203440.O28118@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jsimmons@linux-fbdev.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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