[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJD7tkYxiOZF2F1RxEPTX4nYvAtvHn469JP63KDnifsxR_sQhQ@mail.gmail.com>
Date: Mon, 6 Feb 2023 13:12:04 -0800
From: Yosry Ahmed <yosryahmed@...gle.com>
To: Alistair Popple <apopple@...dia.com>
Cc: linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, jgg@...dia.com, jhubbard@...dia.com,
tjmercier@...gle.com, hannes@...xchg.org, surenb@...gle.com,
mkoutny@...e.com, daniel@...ll.ch,
"Daniel P . Berrange" <berrange@...hat.com>,
Alex Williamson <alex.williamson@...hat.com>
Subject: Re: [PATCH 18/19] mm/mmap: Charge locked memory to pins cgroup
On Sun, Feb 5, 2023 at 11:50 PM Alistair Popple <apopple@...dia.com> wrote:
>
> account_locked_vm() is used to account memory to mm->locked_vm. This
> adds accounting to the pins cgorup as it behaves similarly and should
> be accounted against the same global limit if set.
>
> This means memory must now be unaccounted for correctly, as the cgroup
> typically outlives both the mm and the task. It is assumed that
> callers of account_locked_vm() only do accounting against the current
> task. Callers that need to do accounting against remote tasks should
> use account_pinned_vm() and associated struct vm_account to hold
> references to the cgroup.
>
> Signed-off-by: Alistair Popple <apopple@...dia.com>
> Cc: linux-mm@...ck.org
> Cc: linux-kernel@...r.kernel.org
> ---
> mm/util.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/mm/util.c b/mm/util.c
> index 1ca0dfe..755bada 100644
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -589,15 +589,21 @@ int __account_locked_vm(struct mm_struct *mm, unsigned long pages,
> struct task_struct *task, bool bypass_rlim)
> {
> unsigned long locked_vm, limit;
> + struct pins_cgroup *pins_cg = get_pins_cg(task);
Here we get one ref one the pins cgroup for the entire locked region
that may contain multiple pages, right? During unlock, we drop the
ref. Is it possible that we lock a region (acquiring one ref), and
then unlock it in chunks (dropping multiple refs)?
If this is possible, we may have a problem here. We may need to
acquire one ref per pinned page (not sure if this can overflow). We
may also want to defer the refcount handling to the pins cgroup
controller code, similar to charge_memcg(), a function that tries to
charge and acquires any necessary refs, same for uncharging.
WDYT?
> int ret = 0;
>
> mmap_assert_write_locked(mm);
>
> + if (pins_cg && !pins_try_charge(pins_cg, pages))
> + return -ENOMEM;
> +
> locked_vm = mm->locked_vm;
> if (!bypass_rlim) {
> limit = task_rlimit(task, RLIMIT_MEMLOCK) >> PAGE_SHIFT;
> - if (locked_vm + pages > limit)
> + if (locked_vm + pages > limit) {
> + pins_uncharge(pins_cg, pages);
> ret = -ENOMEM;
> + }
> }
>
> if (!ret)
> @@ -607,6 +613,12 @@ int __account_locked_vm(struct mm_struct *mm, unsigned long pages,
> (void *)_RET_IP_, pages << PAGE_SHIFT, locked_vm << PAGE_SHIFT,
> task_rlimit(task, RLIMIT_MEMLOCK), ret ? " - exceeded" : "");
>
> + pr_debug("%s: [%d] caller %ps %lu %lu/%lu%s\n", __func__, task->pid,
> + (void *)_RET_IP_, pages << PAGE_SHIFT, locked_vm << PAGE_SHIFT,
> + task_rlimit(task, RLIMIT_MEMLOCK), ret ? " - exceeded" : "");
> +
> + if (pins_cg)
> + put_pins_cg(pins_cg);
> return ret;
> }
> EXPORT_SYMBOL_GPL(__account_locked_vm);
> @@ -622,8 +634,18 @@ void __unaccount_locked_vm(struct mm_struct *mm, unsigned long pages)
> {
> unsigned long locked_vm = mm->locked_vm;
>
> + /*
> + * TODO: Convert book3s vio to use pinned vm to ensure
> + * unaccounting happens to the correct cgroup.
> + */
> + struct pins_cgroup *pins_cg = get_pins_cg(current);
> +
> mmap_assert_write_locked(mm);
> WARN_ON_ONCE(pages > locked_vm);
> + if (pins_cg) {
> + pins_uncharge(pins_cg, pages);
> + put_pins_cg(pins_cg);
> + }
> mm->locked_vm = locked_vm - pages;
> }
> EXPORT_SYMBOL_GPL(__unaccount_locked_vm);
> --
> git-series 0.9.1
>
Powered by blists - more mailing lists