mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>, <joro@8bytes.org>,
	<will@kernel.org>, <dwmw2@infradead.org>,
	<baolu.lu@linux.intel.com>, <robin.murphy@arm.com>
Cc: <linux-kernel@vger.kernel.org>,
	<iommu@lists.linux-foundation.org>, <linuxarm@huawei.com>,
	<thunder.leizhen@huawei.com>, <chenxiang66@hisilicon.com>
Subject: Re: [PATCH v10 1/3] iommu: Enhance IOMMU default DMA mode build options
Date: Thu, 3 Jun 2021 18:04:46 +0100	[thread overview]
Message-ID: <18764b43-6c60-eb6d-783f-b7d4fe146b8e@huawei.com> (raw)
In-Reply-To: <c8107ae9-b099-459f-eea4-b9b5a0929ee2@infradead.org>

On 03/06/2021 18:00, Randy Dunlap wrote:
>> +config IOMMU_DEFAULT_STRICT
>> +	bool "strict"
>> +	help
>> +	  For every IOMMU DMA unmap operation, the flush operation of IOTLB and
>> +	  the free operation of IOVA are guaranteed to be done in the unmap
>> +	  function.
>> +
>> +	  This mode is safer than the two above, but it maybe slower in some
> There don't seem to be two above?
> 

Right, it's a remnant from a previous version - will fix, pending other 
reviews

>> +	  high performace scenarios.
> 	       performance
> 

ok

>> +
>> +endchoice

Thanks!

  reply	other threads:[~2021-06-03 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 13:58 [PATCH v10 0/3] " John Garry
2021-06-03 13:58 ` [PATCH v10 1/3] iommu: " John Garry
2021-06-03 17:00   ` Randy Dunlap
2021-06-03 17:04     ` John Garry [this message]
2021-06-04  2:54   ` Leizhen (ThunderTown)
2021-06-04  8:19     ` John Garry
2021-06-03 13:58 ` [PATCH v10 2/3] iommu/vt-d: Add support for " John Garry
2021-06-03 13:58 ` [PATCH v10 3/3] iommu/amd: " John Garry

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=18764b43-6c60-eb6d-783f-b7d4fe146b8e@huawei.com \
    --to=john.garry@huawei.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chenxiang66@hisilicon.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=rdunlap@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=thunder.leizhen@huawei.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

all inboxes | Powered by JetHome®