From: "Gérard Roudier" <groudier@free.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pete Zaitcev <zaitcev@redhat.com>, <stodden@in.tum.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: pci_pool reap?
Date: Sun, 10 Feb 2002 21:20:05 +0100 (CET) [thread overview]
Message-ID: <20020210211352.Q1910-100000@gerard> (raw)
In-Reply-To: <E16a6sw-0005Jw-00@the-village.bc.nu>
On Mon, 11 Feb 2002, Alan Cox wrote:
> > There is a certain controversy about pci_free_consistent called
> > from an interrupt. It seems that most architectures would
> > have no problems, and only arm is problematic. RMK says that
>
> The discussion was about pci_alloc_consistent. The free case seems to be
> explicitly disallowed in all cases.
>
> (from DMA-mapping.txt)
>
> To unmap and free such a DMA region, you call:
>
> pci_free_consistent(dev, size, cpu_addr, dma_handle);
>
> where dev, size are the same as in the above call and cpu_addr and
> dma_handle are the values pci_alloc_consistent returned to you.
> This function may not be called in interrupt context.
Such limitation looks poor implementation to me.
At least, could existing driver interface be clearly documented about what
methods may/may not/might/should/shall/ever will/never will/ etc.. be
called in interrupt context or whatever context and what others may be
called...
...in a different way :-).
Gérard.
next prev parent reply other threads:[~2002-02-11 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1013388420.27877.linux-kernel2news@redhat.com>
2002-02-11 2:49 ` pci_pool reap? Pete Zaitcev
2002-02-11 3:12 ` Alan Cox
2002-02-10 20:20 ` Gérard Roudier [this message]
2002-02-12 2:44 ` David S. Miller
2002-02-11 20:34 ` Gérard Roudier
2002-02-12 15:36 ` Daniel Stodden
2002-02-11 21:10 ` Gérard Roudier
2002-02-12 21:14 ` Daniel Stodden
2002-02-12 15:48 ` Russell King
2002-02-12 15:50 ` David S. Miller
2002-02-12 15:59 ` Russell King
2002-02-12 17:27 ` Daniel Stodden
2002-02-12 15:49 ` David S. Miller
2002-02-11 0:44 Daniel Stodden
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=20020210211352.Q1910-100000@gerard \
--to=groudier@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stodden@in.tum.de \
--cc=zaitcev@redhat.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 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.