From: Tom Rini <trini@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Todd Poynor <tpoynor@mvista.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: consistent_free re-revisited
Date: Thu, 12 Sep 2002 07:51:46 -0700 [thread overview]
Message-ID: <20020912145146.GD13840@opus.bloom.county> (raw)
In-Reply-To: <20020912072315.5346@192.168.4.1>
On Thu, Sep 12, 2002 at 09:23:15AM +0200, Benjamin Herrenschmidt wrote:
> >> That's the least of our worries - the current consistent_alloc() is
> >> badly broken. It breaks the DMA-mapping.txt rules, because it can't
> >> safely be called from interrupt context. I think we need generic
> >> changes (gfp masks to various functions) to fix this sanely.
> >
> >IIRC, to fix the interrupt context bit, we need something like the
> >following, which was Paul's idea, and he said he would talk to Dave M.
> >about it. Did anything ever happen there?
>
> I tend to hate anything that relies on in_interrupt() as they
> are other contexts that will have in_interrupt() cleared but still
> have the same limitations. Typically, anything on the VM path must
> do either GFP_ATOMIC or GFP_NOIO allocations, wether it's running
> at interrupt time or not.
The problem is that the atomic pool is limited, iirc.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-12 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 21:45 consistent_free re-revisited Todd Poynor
2002-09-12 3:26 ` David Gibson
2002-09-12 14:29 ` Tom Rini
2002-09-12 7:23 ` Benjamin Herrenschmidt
2002-09-12 14:51 ` Tom Rini [this message]
2002-09-12 7:49 ` Benjamin Herrenschmidt
2002-09-12 15:23 ` Tom Rini
2002-09-12 8:08 ` Benjamin Herrenschmidt
2002-09-12 17:05 ` Matt Porter
2002-09-12 21:33 ` Todd Poynor
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=20020912145146.GD13840@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tpoynor@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 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.