From: "David S. Miller" <davem@redhat.com>
To: dan@embeddededge.com
Cc: hozer@drgw.net, linux-kernel@vger.kernel.org, groudier@free.fr,
mattl@mvista.com
Subject: Re: pci_alloc_consistent from interrupt == BAD
Date: Fri, 18 Jan 2002 12:32:21 -0800 (PST) [thread overview]
Message-ID: <20020118.123221.85715153.davem@redhat.com> (raw)
In-Reply-To: <3C4875DB.9080402@embeddededge.com>
In-Reply-To: <20020118130209.J14725@altus.drgw.net> <3C4875DB.9080402@embeddededge.com>
From: Dan Malek <dan@embeddededge.com>
Date: Fri, 18 Jan 2002 14:22:03 -0500
> Somehow the docs in DMA-mappings.txt say pci_alloc_consistent is allowed from
> interrupt, but this is a "bad thing" on at least arm and PPC non-cache
> coherent cpus.
This isn't unique to PowerPC or ARM, and has nothing to do with allocating
page tables.
Yes it is in fact unique to those ports...
I don't understand how pci_alloc_consistent could ever be claimed to work
from an interrupt function because it actually allocates pages of memory
for all architectures. Anytime you call alloc_pages() (or friends) you could
potentially block or return an error (out of memory) condition.
If it specifies GFP_ATOMIC, there are no problems from interrupts.
You will see that every port other than the mentioned two above use
GFP_ATOMIC in their pci_alloc_consistent implementation, for this very
reason.
The ARM and PPC ports could set __GFP_HIGH in their page table
allocation calls when invoked via pci_alloc_consistent, and this is
the change I suggest they make. It is a trivial fix whereas backing
out this ability to call pci_alloc_consistent from interrupts is not
a trivial change at all.
next prev parent reply other threads:[~2002-01-18 20:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 19:02 pci_alloc_consistent from interrupt == BAD Troy Benjegerdes
2002-01-18 19:22 ` Dan Malek
2002-01-18 20:32 ` David S. Miller [this message]
2002-01-18 21:29 ` Russell King
2002-01-18 21:33 ` David S. Miller
2002-01-18 21:42 ` 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:43 ` Dan Malek
2002-01-18 20:50 ` Gérard Roudier
[not found] ` <mailman.1011386221.24072.linux-kernel2news@redhat.com>
2002-01-21 23:52 ` Pete Zaitcev
2002-01-22 0:08 ` David S. Miller
2002-01-22 0:20 ` Pete Zaitcev
2002-01-18 20:21 ` Gérard Roudier
2002-01-18 20:38 ` David S. Miller
2002-01-18 21:07 ` Gérard Roudier
2002-01-18 21:13 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
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=20020118.123221.85715153.davem@redhat.com \
--to=davem@redhat.com \
--cc=dan@embeddededge.com \
--cc=groudier@free.fr \
--cc=hozer@drgw.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mattl@mvista.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