public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
	<jean-philippe@linaro.org>, <apopple@nvidia.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>
Subject: Re: [PATCH] iommu/arm-smmu-v3: Add a configurable tlbi_range_max_n_shift for TLBI
Date: Wed, 16 Aug 2023 10:37:36 -0700	[thread overview]
Message-ID: <ZN0JYO/of2qH0krp@Asurada-Nvidia> (raw)
In-Reply-To: <ZN0Iqf9xrCEOOXUJ@nvidia.com>

On Wed, Aug 16, 2023 at 02:34:33PM -0300, Jason Gunthorpe wrote:
> On Wed, Aug 16, 2023 at 10:09:20AM -0700, Nicolin Chen wrote:
> > > This seems convoluted for a uapi, you should just make it
> > > 'invalidate_threshold' in bytes or something simpler.
> > 
> > Hmm. That'd be a direct 64-bit size configuration, and very likely
> > to be at upper 32-bit range, so I feel the value would be very big
> > that might be hard to read.
> 
> hard to read is fine, it is sysfs

OK. I'd just do it in size then.

Thanks
Nic

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-08-16 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 21:57 [PATCH] iommu/arm-smmu-v3: Add a configurable tlbi_range_max_n_shift for TLBI Nicolin Chen
2023-08-16 11:59 ` Jason Gunthorpe
2023-08-16 17:09   ` Nicolin Chen
2023-08-16 17:34     ` Jason Gunthorpe
2023-08-16 17:37       ` Nicolin Chen [this message]

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=ZN0JYO/of2qH0krp@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=apopple@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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