From: Dan Malek <dan@embeddededge.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: hozer@drgw.net, linux-kernel@vger.kernel.org, groudier@free.fr
Subject: Re: pci_alloc_consistent from interrupt == BAD
Date: Fri, 18 Jan 2002 16:46:37 -0500 [thread overview]
Message-ID: <3C4897BD.1080503@embeddededge.com> (raw)
In-Reply-To: <20020118130209.J14725@altus.drgw.net> <3C4875DB.9080402@embeddededge.com> <20020118.123221.85715153.davem@redhat.com> <20020118212949.H2059@flint.arm.linux.org.uk>
Russell King wrote:
> ..... The problem currently is
> that there is no way for the page table allocation functions to know
> that they should be using atomic and emergency pool memory allocations.
Hmmm...I thought they already do this. I always assumed the gfp_flag passed
into alloc_pages would find its way all of the way through the page table
allocation as well. You just have to be ready to handle the case where
it returns with an -ENOMEM :-).
-- Dan
next prev parent reply other threads:[~2002-01-18 21:47 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
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 [this message]
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=3C4897BD.1080503@embeddededge.com \
--to=dan@embeddededge.com \
--cc=groudier@free.fr \
--cc=hozer@drgw.net \
--cc=linux-kernel@vger.kernel.org \
/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