[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240723171001.b06f0a8053efaa7ec40e400e@linux-foundation.org>
Date: Tue, 23 Jul 2024 17:10:01 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: Shakeel Butt <shakeel.butt@...ux.dev>, jpoimboe@...nel.org,
kent.overstreet@...ux.dev, peterz@...radead.org, nphamcs@...il.com,
cerasuolodomenico@...il.com, surenb@...gle.com, lizhijian@...itsu.com,
willy@...radead.org, vbabka@...e.cz, ziy@...dia.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v4] vmstat: Kernel stack usage histogram
On Thu, 18 Jul 2024 22:55:17 -0400 Pasha Tatashin <pasha.tatashin@...een.com> wrote:
> >
> > > +{
> > > + if (used_stack <= 1024)
> > > + this_cpu_inc(vm_event_states.event[KSTACK_1K]);
> >
> > Why not count_vm_event(KSTACK_1K)? Avoiding header include recursion?
>
> I could not include "linux/vmstat.h" into "linux/sched/task_stack.h"
> because it introduces some dependencies such linux/mm.h and
> linux/fs.h, uapi/linux/stat.h, and when all of those are added it
> still fails to compile on some architectures, so it was just simpler
> to stop resolving the conflicts and use this_cpu_inc() directly.
Presumably uninlining stack_not_used() will permit this
to be cleaned up.
Powered by blists - more mailing lists