From: Auger Eric <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Will Deacon <will@kernel.org>,
zhangfei.gao@foxmail.com, QEMU Developers <qemu-devel@nongnu.org>,
Peter Xu <peterx@redhat.com>, qemu-arm <qemu-arm@nongnu.org>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh@kernel.org>,
Eric Auger <eric.auger.pro@gmail.com>
Subject: Re: [PATCH v2 4/9] hw/arm/smmu: Simplify the IOTLB key format
Date: Mon, 6 Jul 2020 16:00:33 +0200 [thread overview]
Message-ID: <932dca70-37dd-ce23-360b-3903ad5910f9@redhat.com> (raw)
In-Reply-To: <CAFEAcA9ipO0x1-7Zu2cm_q+LoKx17D02vsW1=Aks3nHyQzCpaw@mail.gmail.com>
Hi Peter,
On 7/6/20 3:26 PM, Peter Maydell wrote:
> On Thu, 2 Jul 2020 at 16:27, Eric Auger <eric.auger@redhat.com> wrote:
>>
>> Instead of using a Jenkins hash function to generate
>> the key let's just use a 64 bit unsigned integer that
>> contains the asid and the 40 upper bits of the iova.
>> A maximum of 52-bit IOVA is supported. This change in the
>> key format also prepares for the addition of new fields
>> in subsequent patches (granule and level).
>>
>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>
>> diff --git a/hw/arm/smmu-common.c b/hw/arm/smmu-common.c
>> index 7dc8541e8b..5e85e30bdf 100644
>> --- a/hw/arm/smmu-common.c
>> +++ b/hw/arm/smmu-common.c
>> @@ -34,34 +34,17 @@
>>
>> static guint smmu_iotlb_key_hash(gconstpointer v)
>> {
>> - SMMUIOTLBKey *key = (SMMUIOTLBKey *)v;
>> - uint32_t a, b, c;
>> -
>> - /* Jenkins hash */
>> - a = b = c = JHASH_INITVAL + sizeof(*key);
>> - a += key->asid;
>> - b += extract64(key->iova, 0, 32);
>> - c += extract64(key->iova, 32, 32);
>> -
>> - __jhash_mix(a, b, c);
>> - __jhash_final(a, b, c);
>> -
>> - return c;
>> + return (guint)*(const uint64_t *)v;
>> }
>
> So the hash value is now going to be the lower 32
> bits of the key, which is to say bits [40,12] of the IOVA,
> and won't include the ASID at all. Isn't that going to
> result in more hash collisions than would be ideal?
>
> I was going to suggest using the glib builtin g_int64_hash()
> instead, but looking at the source that seems to be the
> identical implementation to this one. I guess that's
> intended for cases where an integer key is really a
> random integer, not one where it's got internal structure
> of different bit fields within it being for different
> purposes.
That's something I did not notice. Would you recommend to keep the
Jenkins hash function then? Note the intel iommu also use the hash
function which only covers the gfn.
Thanks
Eric
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2020-07-06 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 15:26 [PATCH v2 0/9] SMMUv3.2 Range-based TLB Invalidation Support Eric Auger
2020-07-02 15:26 ` [PATCH v2 1/9] hw/arm/smmu-common: Factorize some code in smmu_ptw_64() Eric Auger
2020-07-06 13:11 ` Peter Maydell
2020-07-02 15:26 ` [PATCH v2 2/9] hw/arm/smmu-common: Add IOTLB helpers Eric Auger
2020-07-02 15:26 ` [PATCH v2 3/9] hw/arm/smmu: Introduce smmu_get_iotlb_key() Eric Auger
2020-07-06 13:13 ` Peter Maydell
2020-07-02 15:26 ` [PATCH v2 4/9] hw/arm/smmu: Simplify the IOTLB key format Eric Auger
2020-07-06 13:26 ` Peter Maydell
2020-07-06 14:00 ` Auger Eric [this message]
2020-07-02 15:26 ` [PATCH v2 5/9] hw/arm/smmu: Introduce SMMUTLBEntry for PTW and IOTLB value Eric Auger
2020-07-02 15:26 ` [PATCH v2 6/9] hw/arm/smmu-common: Manage IOTLB block entries Eric Auger
2020-07-07 15:04 ` Peter Maydell
2020-07-02 15:26 ` [PATCH v2 7/9] hw/arm/smmuv3: Introduce smmuv3_s1_range_inval() helper Eric Auger
2020-07-02 15:26 ` [PATCH v2 8/9] hw/arm/smmuv3: Get prepared for range invalidation Eric Auger
2020-07-02 15:26 ` [PATCH v2 9/9] hw/arm/smmuv3: Advertise SMMUv3.2 " Eric Auger
2020-07-06 16:18 ` Robin Murphy
2020-07-06 16:48 ` Auger Eric
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=932dca70-37dd-ce23-360b-3903ad5910f9@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jean-philippe@linaro.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@foxmail.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).