From: Muli Ben-Yehuda <muli@il.ibm.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: [PATCH 1/2] x86: avoid unnecessary low zone allocation in Calgary's alloc_coherent
Date: Thu, 11 Sep 2008 21:10:06 +0300 [thread overview]
Message-ID: <20080911181006.GV6975@il.ibm.com> (raw)
In-Reply-To: <1221142128-28350-2-git-send-email-fujita.tomonori@lab.ntt.co.jp>
On Thu, Sep 11, 2008 at 11:08:47PM +0900, FUJITA Tomonori wrote:
> x86's common alloc_coherent (dma_alloc_coherent in dma-mapping.h) sets
> up the gfp flag according to the device dma_mask but Calgary doesn't
> need it because of virtual mappings. This patch avoids unnecessary low
> zone allocation.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Cc: Alexis Bruemmer <alexisb@us.ibm.com>
> Cc: Muli Ben-Yehuda <muli@il.ibm.com>
Looks good,
Acked-by: Muli Ben-Yehuda <muli@il.ibm.com>
Cheers,
Muli
--
Workshop on I/O Virtualization (WIOV '08)
Co-located with OSDI '08, Dec 2008, San Diego, CA
http://www.usenix.org/wiov08
next prev parent reply other threads:[~2008-09-11 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 14:08 [PATCH 0/2] x86: fixes for the allow_coherent rewrite (tip/x86/iommu) FUJITA Tomonori
2008-09-11 14:08 ` [PATCH 1/2] x86: avoid unnecessary low zone allocation in Calgary's alloc_coherent FUJITA Tomonori
2008-09-11 14:08 ` [PATCH 2/2] x86: gart alloc_coherent does virtual mapppings only when necessary FUJITA Tomonori
2008-09-11 14:16 ` Joerg Roedel
2008-09-14 14:44 ` Ingo Molnar
2008-09-11 18:10 ` Muli Ben-Yehuda [this message]
2008-09-14 14:44 ` [PATCH 1/2] x86: avoid unnecessary low zone allocation in Calgary's alloc_coherent Ingo Molnar
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=20080911181006.GV6975@il.ibm.com \
--to=muli@il.ibm.com \
--cc=alexisb@us.ibm.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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.