From: Christopher Lameter <cl@linux.com>
To: Chintan Pandya <cpandya@codeaurora.org>
Cc: penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] slub: use jitter-free reference while printing age
Date: Thu, 8 Mar 2018 12:12:50 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1803081211230.14668@nuc-kabylake> (raw)
In-Reply-To: <1520492010-19389-1-git-send-email-cpandya@codeaurora.org>
On Thu, 8 Mar 2018, Chintan Pandya wrote:
> In this case, object got freed later but 'age'
> shows otherwise. This could be because, while
> printing this info, we print allocation traces
> first and free traces thereafter. In between,
> if we get schedule out or jiffies increment,
> (jiffies - t->when) could become meaningless.
Could you show the new output style too?
Acked-by: Christoph Lameter <cl@linux.com>
next prev parent reply other threads:[~2018-03-08 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 6:53 Chintan Pandya
2018-03-08 18:12 ` Christopher Lameter [this message]
2018-03-09 5:18 ` Chintan Pandya
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=alpine.DEB.2.20.1803081211230.14668@nuc-kabylake \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=cpandya@codeaurora.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@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