mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gérard Roudier" <groudier@free.fr>
To: "David S. Miller" <davem@redhat.com>
Cc: <hozer@drgw.net>, <linux-kernel@vger.kernel.org>,
	<alan@lxorguk.ukuu.org.uk>, <rmk@arm.linux.org.uk>,
	<dan@embeddededge.com>, <mattl@mvista.com>
Subject: Re: pci_alloc_consistent from interrupt == BAD
Date: Fri, 18 Jan 2002 22:07:09 +0100 (CET)	[thread overview]
Message-ID: <20020118215449.K2042-100000@gerard> (raw)
In-Reply-To: <20020118.123837.21900127.davem@redhat.com>



On Fri, 18 Jan 2002, David S. Miller wrote:

>    From: Gérard Roudier <groudier@free.fr>
>    Date: Fri, 18 Jan 2002 21:21:35 +0100 (CET)
>
>    I have noted that some ports may [ever] require pci_alloc_consistent not
>    to be called from interrupt context. Just I will look into this when time
>    will allow.
>
> Do not bother Gerard, these ports really are broken and
> pci_alloc_consistent must work from interrupts.
>
>    I am not going to ever use not cache coherent hardware, even if I am ready
>    to make the sym driver work reliably on such brain-dead things. Just it is
>    not high priority stuff for now.
>
> Perhaps you misunderstand, it is not "lack of cache coherency" it is
> "cache needs flushing around DMA transfers" and this is handled
> perfectly by PCI DMA interfaces.  It is nothing you should be
> concerned about.

Depends on the OS.

Under Linux, PCI consistent allocation support is a requirement. Let me
cross fingers for this to stay as it is. :)

Under some other (NetBSD, for example, just not to name it :)), such
feature is just a hint and as a result drivers are theorically also
required to care about cache flushing for DMAs that involve driver
internal data structures if full portability is in concern. Btw, I donnot
really use NetBSD O/S but just ported sym-2 to it (NetBSD-1.5 with
coherency being a requirement for driver data structure allocations) as an
exercise.

  Gérard.


  reply	other threads:[~2002-01-18 21:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1011386221.24072.linux-kernel2news@redhat.com>
2002-01-18 19:02 ` Troy Benjegerdes
2002-01-18 19:22   ` Dan Malek
2002-01-18 20:50     ` Gérard Roudier
2002-01-21 23:52     ` Pete Zaitcev
2002-01-18 20:21   ` Gérard Roudier
2002-01-18 20:32   ` David S. Miller
2002-01-18 21:29     ` Russell King
2002-01-18 21:46       ` Dan Malek
2002-01-18 21:55         ` Russell King
2002-01-18 22:13           ` Dan Malek
2002-01-18 21:33     ` David S. Miller
2002-01-18 21:42       ` Russell King
2002-01-18 21:43     ` Dan Malek
2002-01-18 20:38   ` David S. Miller
2002-01-18 21:07     ` Gérard Roudier [this message]
2002-01-18 21:13     ` David S. Miller
2002-01-22  0:08 ` David S. Miller
2002-01-22  0:20   ` Pete Zaitcev
2002-01-19 17:21 David Brownell

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=20020118215449.K2042-100000@gerard \
    --to=groudier@free.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dan@embeddededge.com \
    --cc=davem@redhat.com \
    --cc=hozer@drgw.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattl@mvista.com \
    --cc=rmk@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®