From: Andrey Konovalov <andreyknvl@gmail.com>
To: Marco Elver <elver@google.com>
Cc: andrey.konovalov@linux.dev,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
kasan-dev@googlegroups.com, Evgenii Stepanov <eugenis@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH 14/15] stackdepot: allow users to evict stack traces
Date: Mon, 4 Sep 2023 20:47:09 +0200 [thread overview]
Message-ID: <CA+fCnZcwftJtROmUzhvqczxHvCxTEUmhoONPXPzX23OWMNm_Kg@mail.gmail.com> (raw)
In-Reply-To: <ZO8Jwy5SAgkrQ5Qz@elver.google.com>
On Wed, Aug 30, 2023 at 11:20 AM Marco Elver <elver@google.com> wrote:
>
> > +/**
> > + * stack_depot_evict - Drop a reference to a stack trace from stack depot
> > + *
> > + * @handle: Stack depot handle returned from stack_depot_save()
> > + *
> > + * The stack trace gets fully removed from stack depot once all references
>
> "gets fully removed" -> "is evicted" ?
>
> > + * to it has been dropped (once the number of stack_depot_evict calls matches
>
> "has been" -> "have been"
Will fix both in v2. Thanks!
next prev parent reply other threads:[~2023-09-04 18:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 17:11 [PATCH 00/15] stackdepot: allow evicting stack traces andrey.konovalov
2023-08-29 17:11 ` [PATCH 01/15] stackdepot: check disabled flag when fetching andrey.konovalov
2023-08-30 7:40 ` Alexander Potapenko
2023-08-29 17:11 ` [PATCH 02/15] stackdepot: simplify __stack_depot_save andrey.konovalov
2023-08-30 7:41 ` Alexander Potapenko
2023-08-29 17:11 ` [PATCH 03/15] stackdepot: drop valid bit from handles andrey.konovalov
2023-08-30 7:43 ` Alexander Potapenko
2023-08-29 17:11 ` [PATCH 04/15] stackdepot: add depot_fetch_stack helper andrey.konovalov
2023-08-30 7:47 ` Alexander Potapenko
2023-08-29 17:11 ` [PATCH 05/15] stackdepot: use fixed-sized slots for stack records andrey.konovalov
2023-08-30 8:21 ` Alexander Potapenko
2023-09-13 17:07 ` Andrey Konovalov
2023-09-15 10:36 ` Alexander Potapenko
2023-08-29 17:11 ` [PATCH 06/15] stackdepot: fix and clean-up atomic annotations andrey.konovalov
2023-08-30 8:34 ` Marco Elver
2023-09-04 18:45 ` Andrey Konovalov
2023-08-29 17:11 ` [PATCH 07/15] stackdepot: rework helpers for depot_alloc_stack andrey.konovalov
2023-08-29 17:11 ` [PATCH 08/15] stackdepot: rename next_pool_required to new_pool_required andrey.konovalov
2023-08-30 8:29 ` Alexander Potapenko
2023-08-29 17:11 ` [PATCH 09/15] stackdepot: store next pool pointer in new_pool andrey.konovalov
2023-08-29 17:11 ` [PATCH 10/15] stackdepot: store free stack records in a freelist andrey.konovalov
2023-08-29 17:11 ` [PATCH 11/15] stackdepot: use read/write lock andrey.konovalov
2023-08-30 9:13 ` Marco Elver
2023-09-04 18:46 ` Andrey Konovalov
2023-09-05 16:19 ` Marco Elver
2023-09-13 17:08 ` Andrey Konovalov
2024-01-02 12:59 ` Marco Elver
2024-01-09 3:27 ` Andrey Konovalov
2023-08-29 17:11 ` [PATCH 12/15] stackdepot: add refcount for records andrey.konovalov
2023-08-30 9:32 ` Marco Elver
2023-09-04 18:46 ` Andrey Konovalov
2023-09-04 18:55 ` Marco Elver
2023-09-13 17:07 ` Andrey Konovalov
2023-09-01 13:06 ` Kuan-Ying Lee (李冠穎)
2023-09-04 18:46 ` Andrey Konovalov
2023-08-29 17:11 ` [PATCH 13/15] stackdepot: add backwards links to hash table buckets andrey.konovalov
2023-08-30 9:24 ` Marco Elver
2023-09-13 17:07 ` Andrey Konovalov
2023-08-29 17:11 ` [PATCH 14/15] stackdepot: allow users to evict stack traces andrey.konovalov
2023-08-30 9:20 ` Marco Elver
2023-09-04 18:47 ` Andrey Konovalov [this message]
2023-08-29 17:11 ` [PATCH 15/15] kasan: use stack_depot_evict for tag-based modes andrey.konovalov
2023-08-30 9:38 ` Marco Elver
2023-09-04 18:48 ` Andrey Konovalov
2023-09-04 18:58 ` Marco Elver
2023-09-13 17:08 ` Andrey Konovalov
2023-08-30 7:46 ` [PATCH 00/15] stackdepot: allow evicting stack traces Vlastimil Babka
2023-09-04 18:45 ` Andrey Konovalov
2023-09-05 2:48 ` Kuan-Ying Lee (李冠穎)
2023-09-13 17:10 ` Andrey Konovalov
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=CA+fCnZcwftJtROmUzhvqczxHvCxTEUmhoONPXPzX23OWMNm_Kg@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.