linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: David Wang <00107082@163.com>,
	kent.overstreet@linux.dev,  akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 2/2] alloc_tag: keep codetag iterator active between read() calls
Date: Fri, 09 May 2025 12:46:06 -0700	[thread overview]
Message-ID: <294d0743c0b2e5c409857ef81a6fe8baaf87727f.camel@linux.intel.com> (raw)
In-Reply-To: <CAJuCfpHB8T8daanvE_wowRD9-sAo30rtCcFfMPZL_751+KSs5w@mail.gmail.com>

On Fri, 2025-05-09 at 12:36 -0700, Suren Baghdasaryan wrote:
> On Fri, May 9, 2025 at 11:33 AM Tim Chen <tim.c.chen@linux.intel.com> wrote:
> > 
> > On Sat, 2025-05-10 at 01:39 +0800, David Wang wrote:
> > > 
> > > 
> > > Signed-off-by: David Wang <00107082@163.com>
> 
> Acked-by: Suren Baghdasaryan <surenb@google.com>
> 
> > > ---
> > >  lib/alloc_tag.c | 29 ++++++++++-------------------
> > >  1 file changed, 10 insertions(+), 19 deletions(-)
> > > 
> > > diff --git a/lib/alloc_tag.c b/lib/alloc_tag.c
> > > index 25ecc1334b67..fdd5887769a6 100644
> > > --- a/lib/alloc_tag.c
> > > +++ b/lib/alloc_tag.c
> > > @@ -45,21 +45,16 @@ struct allocinfo_private {
> > >  static void *allocinfo_start(struct seq_file *m, loff_t *pos)
> > >  {
> > >       struct allocinfo_private *priv;
> > > -     struct codetag *ct;
> > >       loff_t node = *pos;
> > > 
> > > -     priv = kzalloc(sizeof(*priv), GFP_KERNEL);
> > > -     m->private = priv;
> > > -     if (!priv)
> > > -             return NULL;
> > > -
> > > -     priv->print_header = (node == 0);
> > > +     priv = (struct allocinfo_private *)m->private;
> > >       codetag_lock_module_list(alloc_tag_cttype, true);
> > > -     priv->iter = codetag_get_ct_iter(alloc_tag_cttype);
> > > -     while ((ct = codetag_next_ct(&priv->iter)) != NULL && node)
> > > -             node--;
> > > -
> > > -     return ct ? priv : NULL;
> > > +     if (node == 0) {
> > > +             priv->print_header = true;
> > > +             priv->iter = codetag_get_ct_iter(alloc_tag_cttype);
> > > +             codetag_next_ct(&priv->iter);
> > > +     }
> > 
> > Do you need to skip print header when *pos != 0? i.e add
> 
> Technically not needed since proc_create_seq_private() allocates
> seq->private using kzalloc(), so the initial value of
> priv->print_header is always false.

But we'll start with first call to allocinfo_start() with *pos == 0, 
then print_header will be initialized to true.
Will there be subsequent calls of allocinfo_start() with *pos !=0,
but priv->print_header stays at 0? 

Tim
> 
> > 
> >         } else {
> >                 priv->print_header = false;
> >         }
> > 
> > Tim
> > 
> > > +     return priv->iter.ct ? priv : NULL;
> > >  }
> > > 
> > 


  reply	other threads:[~2025-05-09 19:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 17:55 [PATCH] alloc_tag: avoid mem alloc and iter reset when reading allocinfo David Wang
2025-05-07 18:19 ` David Wang
2025-05-07 23:42   ` [PATCH] " Suren Baghdasaryan
2025-05-08  0:01     ` Kent Overstreet
2025-05-08  3:06       ` David Wang
2025-05-08  3:31         ` Kent Overstreet
2025-05-08  3:35           ` David Wang
2025-05-08  4:07             ` Kent Overstreet
2025-05-08  5:51               ` David Wang
2025-05-08 13:33                 ` Kent Overstreet
2025-05-08 16:24                   ` David Wang
2025-05-08 16:34                     ` Kent Overstreet
2025-05-08 16:58                       ` David Wang
2025-05-08 17:17                         ` David Wang
2025-05-08 17:26                           ` Kent Overstreet
2025-05-08  2:24     ` David Wang
2025-05-07 23:36 ` Suren Baghdasaryan
2025-05-08  3:10   ` David Wang
2025-05-08 15:32   ` David Wang
2025-05-08 21:41     ` Suren Baghdasaryan
2025-05-09  5:51 ` [PATCH 1/2] alloc_tag: add timestamp to codetag iterator David Wang
2025-05-09 16:10   ` Suren Baghdasaryan
2025-05-09 16:16     ` David Wang
2025-05-09  5:53 ` [PATCH 2/2] alloc_tag: keep codetag iterator cross read() calls David Wang
2025-05-09 17:34   ` Suren Baghdasaryan
2025-05-09 17:45     ` David Wang
2025-05-09 17:38 ` [PATCH v2 1/2] alloc_tag: add sequence number for module and iterator David Wang
2025-05-09 19:25   ` Suren Baghdasaryan
2025-06-09  6:42     ` [PATCH v3 " David Wang
2025-06-09 16:41       ` Suren Baghdasaryan
2025-05-09 17:39 ` [PATCH v2 2/2] alloc_tag: keep codetag iterator active between read() calls David Wang
2025-05-09 18:33   ` Tim Chen
2025-05-09 19:36     ` Suren Baghdasaryan
2025-05-09 19:46       ` Tim Chen [this message]
2025-05-09 20:46         ` Suren Baghdasaryan
2025-05-09 21:15           ` Suren Baghdasaryan
2025-05-10  3:10             ` David Wang
2025-05-10  3:30               ` Suren Baghdasaryan
2025-05-10  3:58                 ` David Wang
2025-05-10  4:03                   ` Suren Baghdasaryan
2025-06-09  6:44                     ` [PATCH v3 2/2] alloc_tag: keep codetag iterator active between read() David Wang
2025-06-10 16:22                       ` Suren Baghdasaryan
2025-05-10  3:35         ` [PATCH v2 2/2] alloc_tag: keep codetag iterator active between read() calls David Wang
2025-05-10  3:25     ` David Wang

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=294d0743c0b2e5c409857ef81a6fe8baaf87727f.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=00107082@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=surenb@google.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).