From: Takashi Iwai <tiwai@suse.de>
To: Giuliano Pochini <pochini@shiny.it>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: PCI write barrier
Date: Fri, 23 May 2003 12:30:14 +0200 [thread overview]
Message-ID: <s5h8ysyq7k9.wl@alsa2.suse.de> (raw)
In-Reply-To: <XFMail.20030522151644.pochini@shiny.it>
At Thu, 22 May 2003 15:16:44 +0200 (CEST),
Giuliano Pochini wrote:
>
>
> I was reading this: http://people.redhat.com/arjanv/olspaper.pdf. It
> says (page 4, par5.1) the PCI controller is allowed to delay writes
> as long as it likes and a read operation flushes all pending writes.
> Is it true ? I had a quick look at some ALSA drivers, but I couldn't
> find any barrier or any apparent useless read after a write.
you are right.
this issue is not taken into account in most of drivers codes, in the
case of non-memory-mapped access.
i think this should be solved in the kernel core side, e.g. providing
special pci access functions set, though.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-23 10:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 20:10 documentation - yeah right! Cliff Bradshaw
2003-05-20 20:16 ` Jaroslav Kysela
2003-05-20 20:31 ` Josh Green
2003-05-20 20:52 ` Kai Vehmanen
2003-05-20 22:11 ` David Stuart
2003-05-20 22:08 ` Paul Davis
2003-05-20 23:53 ` Drake Wilson
2003-05-21 5:02 ` Patrick Shirkey
2003-05-21 7:34 ` Giuliano Pochini
2003-05-21 14:43 ` Richard Cochran
2003-05-21 15:24 ` Paul Davis
2003-05-21 15:50 ` Paul Davis
[not found] ` <200305211518.h4LFI2jE027163@mail.cs.umass.edu>
2003-05-21 15:59 ` Richard Cochran
2003-05-21 16:52 ` Kai Vehmanen
2003-05-21 17:16 ` Richard Cochran
2003-05-21 17:36 ` Kai Vehmanen
2003-05-21 17:39 ` Jaroslav Kysela
2003-05-21 17:49 ` Paul Davis
2003-05-21 17:03 ` Paul Davis
[not found] ` <200305211657.h4LGvKjE024721@mail.cs.umass.edu>
2003-05-21 18:08 ` Richard Cochran
2003-05-22 1:28 ` Patrick Shirkey
2003-05-21 16:09 ` Richard Cochran
2003-05-21 16:44 ` Paul Davis
2003-05-22 13:16 ` PCI write barrier Giuliano Pochini
2003-05-23 10:30 ` Takashi Iwai [this message]
2003-05-22 12:47 ` documentation - yeah right! Takashi Iwai
2003-05-22 13:39 ` Jaroslav Kysela
2003-05-22 14:51 ` Pieter Palmers
2003-05-22 14:18 ` Richard Cochran
2003-05-22 15:33 ` Takashi Iwai
2003-05-22 16:57 ` Jack O'Quin
2003-05-22 17:03 ` Patrick Shirkey
2003-05-22 17:08 ` Richard Cochran
2003-07-11 0:23 ` i810 - no sound from cvs snapshot Richard Cochran
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=s5h8ysyq7k9.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pochini@shiny.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.