linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, joerg.roedel@amd.com, tony.luck@intel.com,
	linux-ia64@vger.kernel.org, iommu@lists.linux-foundation.org,
	fujita.tomonori@lab.ntt.co.jp
Subject: [PATCH 0/5] fix exhaustion of ZONE_DMA with swiotlb (in x86 tree)
Date: Mon,  8 Sep 2008 18:10:09 +0900	[thread overview]
Message-ID: <1220865014-1169-1-git-send-email-fujita.tomonori@lab.ntt.co.jp> (raw)

This patchset (against tip/master) fixes the problem that swiotlb
exhausts ZONE_DMA:

http://lkml.org/lkml/2008/8/31/16

The root problem is that swiotlb_alloc_coherent always use ZONE_DMA,
which is fine for IA64 but not for x86_64.

This patchset makes the callers set up the gfp flags so that
swiotlb_alloc_coherent can stop playing with the gfp flags.

I think that it would be better to remove the allocation code in
swiotlb_alloc_coherent theoretically (what swiotlb should do is taking
care of the swiotlb memory. And swiotlb_alloc_coherent is not useful
since we use it only when we can't allocate memory reachable by the
device or we are in out of memory). But that code works for both x86
and IA64 so it's not so bad, I guess.

#1 is for IA64, #2-4 for x86, and #5 is for swiotlb.

=
 arch/ia64/include/asm/dma-mapping.h |    4 ++-
 arch/x86/kernel/pci-nommu.c         |   21 +------------------
 include/asm-x86/dma-mapping.h       |   37 +++++++++++++++++++++++++++++++---
 lib/swiotlb.c                       |    7 ------
 4 files changed, 37 insertions(+), 32 deletions(-)



             reply	other threads:[~2008-09-08  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  9:10 FUJITA Tomonori [this message]
2008-09-08  9:10 ` [PATCH 1/5] ia64: dma_alloc_coherent always use GFP_DMA FUJITA Tomonori
2008-09-08  9:10   ` [PATCH 2/5] x86: move pci-nommu's dma_mask check to common code FUJITA Tomonori
2008-09-08  9:10     ` [PATCH 3/5] x86: fix nommu_alloc_coherent allocation with NULL device argument FUJITA Tomonori
2008-09-08  9:10       ` [PATCH 4/5] x86: dma_alloc_coherent sets gfp flags properly FUJITA Tomonori
2008-09-08  9:10         ` [PATCH 5/5] swiotlb: remove GFP_DMA hack in swiotlb_alloc_coherent FUJITA Tomonori
2008-09-08 12:02           ` Joerg Roedel
2008-09-08 12:01         ` [PATCH 4/5] x86: dma_alloc_coherent sets gfp flags properly Joerg Roedel
2008-09-08 12:01       ` [PATCH 3/5] x86: fix nommu_alloc_coherent allocation with NULL device argument Joerg Roedel
2008-09-08 12:01     ` [PATCH 2/5] x86: move pci-nommu's dma_mask check to common code Joerg Roedel
2008-09-08 12:00 ` [PATCH 0/5] fix exhaustion of ZONE_DMA with swiotlb (in x86 tree) Joerg Roedel
2008-09-08 13:52   ` Ingo Molnar
2008-09-09 10:41 ` KAMEZAWA Hiroyuki

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=1220865014-1169-1-git-send-email-fujita.tomonori@lab.ntt.co.jp \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tony.luck@intel.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 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).