linux-kernel - Re: [RFC PATCH V4 1/1] swiotlb: Split up single swiotlb lock

Open Source and information security mailing list archives

Message-ID: <09751b9b-0912-d2f2-5636-cde6db6afaa3@oracle.com>
Date:   Wed, 22 Jun 2022 05:55:46 -0700
From:   Dongli Zhang <dongli.zhang@...cle.com>
To:     Christoph Hellwig <hch@...radead.org>,
        Tianyu Lan <ltykernel@...il.com>
Cc:     linux-hyperv@...r.kernel.org, linux-doc@...r.kernel.org,
        kys@...rosoft.com, wei.liu@...nel.org,
        Andi Kleen <ak@...ux.intel.com>, corbet@....net,
        damien.lemoal@...nsource.wdc.com, michael.h.kelley@...rosoft.com,
        andi.kleen@...el.com, bp@...e.de, parri.andrea@...il.com,
        thomas.lendacky@....com, Tianyu Lan <Tianyu.Lan@...rosoft.com>,
        paulmck@...nel.org, kirill.shutemov@...el.com,
        songmuchun@...edance.com, tglx@...utronix.de,
        akpm@...ux-foundation.org, rdunlap@...radead.org,
        linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
        vkuznets@...hat.com, robin.murphy@....com
Subject: Re: [RFC PATCH V4 1/1] swiotlb: Split up single swiotlb lock

I will build the next RFC version of 64-bit swiotlb on top of this patch (or
next version of this patch), so that it will render a more finalized view of
32-bt/64-bit plus multiple area.

Thank you very much!

Dongli Zhang

On 6/22/22 3:54 AM, Christoph Hellwig wrote:
> Thanks,
> 
> this looks pretty good to me.  A few comments below:
> 
> On Fri, Jun 17, 2022 at 10:47:41AM -0400, Tianyu Lan wrote:
>> +/**
>> + * struct io_tlb_area - IO TLB memory area descriptor
>> + *
>> + * This is a single area with a single lock.
>> + *
>> + * @used:	The number of used IO TLB block.
>> + * @index:	The slot index to start searching in this area for next round.
>> + * @lock:	The lock to protect the above data structures in the map and
>> + *		unmap calls.
>> + */
>> +struct io_tlb_area {
>> +	unsigned long used;
>> +	unsigned int index;
>> +	spinlock_t lock;
>> +};
> 
> This can go into swiotlb.c.
> 
>> +void __init swiotlb_adjust_nareas(unsigned int nareas);
> 
> And this should be marked static.
> 
>> +#define DEFAULT_NUM_AREAS 1
> 
> I'd drop this define, the magic 1 and a > 1 comparism seems to
> convey how it is used much better as the checks aren't about default
> or not, but about larger than one.
> 
> I also think that we want some good way to size the default, e.g.
> by number of CPUs or memory size.
> 
>> +void __init swiotlb_adjust_nareas(unsigned int nareas)
>> +{
>> +	if (!is_power_of_2(nareas)) {
>> +		pr_err("swiotlb: Invalid areas parameter %d.\n", nareas);
>> +		return;
>> +	}
>> +
>> +	default_nareas = nareas;
>> +
>> +	pr_info("area num %d.\n", nareas);
>> +	/* Round up number of slabs to the next power of 2.
>> +	 * The last area is going be smaller than the rest if
>> +	 * default_nslabs is not power of two.
>> +	 */
> 
> Please follow the normal kernel comment style with a /* on its own line.
> 
> _______________________________________________
> iommu mailing list
> iommu@...ts.linux-foundation.org
> https://urldefense.com/v3/__https://lists.linuxfoundation.org/mailman/listinfo/iommu__;!!ACWV5N9M2RV99hQ!Jd_DYgd6_uOF8IPr8h1tratEG51zFXtwVpaPa_OW3AEJlWe8gOnmA_fGOdaFUfsVcj1sT5oYw2j4vacY$ 
> 

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives