public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Takashi Iwai" <tiwai@suse.de>, "Christoph Hellwig" <hch@lst.de>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	"Christian König" <christian.koenig@amd.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: [PATCH] swiotlb: Fix unexpected swiotlb_alloc_coherent() failures
Date: Tue, 10 Apr 2018 20:10:20 +0200	[thread overview]
Message-ID: <20180410181020.GA28565@lst.de> (raw)
In-Reply-To: <40618b9c-786d-7f5f-3f5b-fc1dd8375846@arm.com>

On Tue, Apr 10, 2018 at 06:50:04PM +0100, Robin Murphy wrote:
> In the first one, the machine appears to have enough RAM that most of it is 
> beyond the device's 36-bit DMA mask, thus it's fairly likely for the 
> initial direct alloc to come back with something unsuitable.

But we should try a GFP_DMA32 allocation first, so this is a bit
surprising.

  reply	other threads:[~2018-04-10 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 17:05 [PATCH] swiotlb: Fix unexpected swiotlb_alloc_coherent() failures Takashi Iwai
2018-04-10 17:06 ` Christoph Hellwig
2018-04-10 17:07   ` Takashi Iwai
2018-04-10 17:50     ` Robin Murphy
2018-04-10 18:10       ` Christoph Hellwig [this message]
2018-04-11  7:28         ` Takashi Iwai
2018-04-12  6:02           ` Christoph Hellwig
2018-04-12  8:03             ` Takashi Iwai
2018-04-12  8:19               ` Takashi Iwai
2018-04-12  8:27                 ` Takashi Iwai
2018-04-12 10:32                   ` Robin Murphy
2018-04-15  8:43                     ` Takashi Iwai

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=20180410181020.GA28565@lst.de \
    --to=hch@lst.de \
    --cc=christian.koenig@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tiwai@suse.de \
    /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