[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220519123255.543b8db6@gandalf.local.home>
Date: Thu, 19 May 2022 12:32:55 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Vasily Averin <vvs@...nvz.org>
Cc: YoPOhRctb8wwbmY5@...bon, Shakeel Butt <shakeelb@...gle.com>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Vlastimil Babka <vbabka@...e.cz>,
Matthew Wilcox <willy@...radead.org>,
Hyeonggon Yoo <42.hyeyoo@...il.com>,
Muchun Song <songmuchun@...edance.com>, kernel@...nvz.org,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
Joonsoo Kim <iamjoonsoo.kim@....com>,
David Rientjes <rientjes@...gle.com>,
Pekka Enberg <penberg@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH v3] tracing: add 'accounted' entry into output of
allocation tracepoints
On Thu, 19 May 2022 19:29:36 +0300
Vasily Averin <vvs@...nvz.org> wrote:
> Frankly speaking I vote for performance with both hands.
> However I'm still would like to avoid new sparse warnings.
> Christoph Hellwig just recently taught me, "never add '__force' before
> thinking hard about them", but in this case I would need to use it three times.
>
> I found that bitwise typecasts can be avoided by using translation unions.
>
> What do you think about following trick?
It's really up to you memory management folks. Although I may need to
update libtraceevent to handle the union case. That may be a bit tricky.
-- Steve
Powered by blists - more mailing lists