From: Christoph Lameter <cl@linux-foundation.org>
To: Roger Oksanen <roger.oksanen@cs.helsinki.fi>
Cc: linux-mm <linux-mm@kvack.org>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [RFC,PATCH 2/2] dmapool: Honor GFP_* flags.
Date: Wed, 2 Dec 2009 16:05:51 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.00.0912021558490.6282@router.home> (raw)
In-Reply-To: <200912022339.55552.roger.oksanen@cs.helsinki.fi>
On Wed, 2 Dec 2009, Roger Oksanen wrote:
> That would fundamentally change how the pool allocator works. Currently it
> waits on its own wait queue for returned memory from dma_pool_free(..).
Plus it also has a timeout. What usually triggers first? Repeated attempts
and a timeout... All smells like heuristics that better be avoided.
> Waiting in the page allocator won't allow it to claim memory returned there.
If __GFP_WAIT is set then the page allocator can perform direct reclaim
getting you the memory you want!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-12-02 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 13:18 [RFC,PATCH 0/2] dmapool: allocation gfp changes Roger Oksanen
2009-12-02 13:20 ` [RFC,PATCH 1/2] dmapool: Don't warn when allowed to retry allocation Roger Oksanen
2009-12-02 19:56 ` Christoph Lameter
2009-12-02 21:22 ` Roger Oksanen
2009-12-02 13:23 ` [RFC,PATCH 2/2] dmapool: Honor GFP_* flags Roger Oksanen
2009-12-02 20:00 ` Christoph Lameter
2009-12-02 21:39 ` Roger Oksanen
2009-12-02 22:05 ` Christoph Lameter [this message]
2009-12-03 12:10 ` Mel Gorman
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=alpine.DEB.2.00.0912021558490.6282@router.home \
--to=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=roger.oksanen@cs.helsinki.fi \
/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