From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: liyihang6@hisilicon.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, will@kernel.org, hch@lst.de
Subject: Re: [RFC PATCH] dma-iommu: Add iommu_dma_max_mapping_size()
Date: Wed, 18 May 2022 15:12:37 +0200 [thread overview]
Message-ID: <20220518131237.GA26019@lst.de> (raw)
In-Reply-To: <f5b78c9c-312e-70ab-ecbb-f14623a4b6e3@arm.com>
On Tue, May 17, 2022 at 11:40:52AM +0100, Robin Murphy wrote:
> Indeed, sorry but NAK for this being nonsense. As I've said at least once
> before, if the unnecessary SAC address allocation attempt slows down your
> workload, make it not do that in the first place. If you don't like the
> existing command-line parameter then fine, there are plenty of other
> options, it just needs to be done in a way that doesn't break x86 systems
> with dodgy firmware, as my first attempt turned out to.
What broke x86?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-05-18 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 13:06 [RFC PATCH] dma-iommu: Add iommu_dma_max_mapping_size() John Garry via iommu
2022-05-17 8:38 ` Christoph Hellwig
2022-05-17 9:02 ` John Garry via iommu
2022-05-17 9:11 ` Christoph Hellwig
2022-05-17 10:40 ` Robin Murphy
2022-05-17 11:26 ` John Garry via iommu
2022-05-17 12:02 ` Robin Murphy
2022-05-17 13:50 ` John Garry via iommu
2022-05-18 13:13 ` Christoph Hellwig
2022-05-20 8:51 ` Joerg Roedel
2022-05-18 13:12 ` Christoph Hellwig [this message]
2022-05-18 13:45 ` Robin Murphy
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=20220518131237.GA26019@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liyihang6@hisilicon.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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).