mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "zhangzekun (A)" <zhangzekun11@huawei.com>
To: Ethan Zhao <haifeng.zhao@linux.intel.com>
Cc: <joro@8bytes.org>, <will@kernel.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <john.g.garry@oracle.com>,
	<dheerajkumar.srivastava@amd.com>, <jsnitsel@redhat.com>,
	Ido Schimmel <idosch@idosch.org>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v3 0/2] iommu/iova: Make the rcache depot properly flexible
Date: Sat, 6 Jan 2024 15:07:21 +0800	[thread overview]
Message-ID: <20924c0f-b752-4f58-91ce-21ed3b305481@huawei.com> (raw)
In-Reply-To: <f8ae34f0-dab2-48fa-b3f8-5e969ed028b7@linux.intel.com>



在 2024/1/6 12:21, Ethan Zhao 写道:
>
> On 1/2/2024 3:24 PM, Ido Schimmel wrote:
>> On Thu, Dec 28, 2023 at 02:23:20PM +0200, Ido Schimmel wrote:
>>> On Tue, Sep 12, 2023 at 05:28:04PM +0100, Robin Murphy wrote:
>>>> v2: 
>>>> https://lore.kernel.org/linux-iommu/cover.1692641204.git.robin.murphy@arm.com/
>>>>
>>>> Hi all,
>>>>
>>>> I hope this is good to go now, just fixed the locking (and threw
>>>> lockdep at it to confirm, which of course I should have done to begin
>>>> with...) and picked up tags.
>>> Hi,
>>>
>>> After pulling the v6.7 changes we started seeing the following memory
>>> leaks [1] of 'struct iova_magazine'. I'm not sure how to reproduce it,
>>> which is why I didn't perform bisection. However, looking at the
>>> mentioned code paths, they seem to have been changed in v6.7 as part of
>>> this patchset. I reverted both patches and didn't see any memory leaks
>>> when running a full regression (~10 hours), but I will repeat it to be
>>> sure.
>> FYI, we didn't see the leaks since reverting these two patches whereas
>> before we saw them almost everyday, so I'm quite sure they introduced
>> the leaks.
>
> Seems some magazines were not freed when one CPU is dead (hot 
> unplugged) ?
>
> static void free_cpu_cached_iovas(unsigned int cpu, struct iova_domain 
> *iovad)
> {
>     struct iova_cpu_rcache *cpu_rcache;
>     struct iova_rcache *rcache;
>     unsigned long flags;
>     int i;
>
>     for (i = 0; i < IOVA_RANGE_CACHE_MAX_SIZE; ++i) {
>         rcache = &iovad->rcaches[i];
>         cpu_rcache = per_cpu_ptr(rcache->cpu_rcaches, cpu);
>         spin_lock_irqsave(&cpu_rcache->lock, flags);
>         iova_magazine_free_pfns(cpu_rcache->loaded, iovad);
>
> +     iova_magazine_free(cpu_rcache->loaded);
>
>         iova_magazine_free_pfns(cpu_rcache->prev, iovad);
>
> +     iova_magazine_free(cpu_rcache->prev);
>
>         spin_unlock_irqrestore(&cpu_rcache->lock, flags);
>     }
> }
It seems cpu_rcache->loaded and cpu_rcache->prev will be freed in 
free_iova_rcaches(), and it should not cause memory leak because 
iova_magazine_free() will be called for each possible cpu.
free_cpu_cached_iovas() is used to free cached iovas in magazines.

Thanks,
Zekun



  reply	other threads:[~2024-01-06  7:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 16:28 Robin Murphy
2023-09-12 16:28 ` [PATCH v3 1/2] iommu/iova: Make the rcache depot scale better Robin Murphy
2023-09-12 16:28 ` [PATCH v3 2/2] iommu/iova: Manage the depot list size Robin Murphy
2023-09-25 10:08 ` [PATCH v3 0/2] iommu/iova: Make the rcache depot properly flexible Joerg Roedel
2023-12-28 12:23 ` Ido Schimmel
2024-01-02  7:24   ` Ido Schimmel
2024-01-03  8:38     ` Joerg Roedel
2024-01-06  4:21     ` Ethan Zhao
2024-01-06  7:07       ` zhangzekun (A) [this message]
2024-01-06  7:33         ` Ethan Zhao
2024-01-06  4:03   ` Ethan Zhao
2024-01-08  3:13   ` Ethan Zhao
2024-01-08 17:35   ` Robin Murphy
2024-01-09  5:54     ` Ethan Zhao
2024-01-09  6:23       ` Ethan Zhao
2024-01-09 11:26         ` Robin Murphy
2024-01-10  0:52           ` Ethan Zhao
2024-01-09 17:21     ` Ido Schimmel
2024-01-10 12:48       ` Robin Murphy
2024-01-10 14:00         ` Ido Schimmel
2024-01-10 17:58         ` Catalin Marinas
2024-01-11  8:20           ` Ido Schimmel
2024-01-11 10:13             ` Catalin Marinas
2024-01-12 15:31               ` Ido Schimmel
2024-01-15  7:17                 ` Ido Schimmel
2024-10-28  8:04                   ` Ido Schimmel
2024-10-28 17:45                     ` Catalin Marinas

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=20924c0f-b752-4f58-91ce-21ed3b305481@huawei.com \
    --to=zhangzekun11@huawei.com \
    --cc=dheerajkumar.srivastava@amd.com \
    --cc=haifeng.zhao@linux.intel.com \
    --cc=idosch@idosch.org \
    --cc=iommu@lists.linux.dev \
    --cc=john.g.garry@oracle.com \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --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

all inboxes | Powered by JetHome®