From: James Bottomley <James.Bottomley@steeleye.com>
To: "David S. Miller" <davem@redhat.com>
Cc: James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: [BK-2.5] Update arm implementation of DMA API to include GFP_
Date: Tue, 14 Jan 2003 10:41:51 -0500 [thread overview]
Message-ID: <200301141541.h0EFfpA02417@localhost.localdomain> (raw)
James.Bottomley@SteelEye.com said:
> Is this really safe? Maybe ARM needs to use GFP_ATOMIC all the time
> for a specific reason, such as where and how it maps the cpu side
> mappings of the memory?
According to Russell King, yes.
The PA-RISC one should also be correct. Actually, to be honest, there's a
longstanding issue in the pa-risc code where we can potentially allocate a
page table using GFP_KERNEL in pci_alloc_consistent() when we obtain the
mapping resources. I can argue that we never go down this path in practice,
but it does make GFP_ATOMIC allocations look unsafe on the platform.
James
reply other threads:[~2003-01-14 15:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200301141541.h0EFfpA02417@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=davem@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).