From: Dave Hansen <dave.hansen@intel.com>
To: George Amvrosiadis <gamvrosi@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/3] new feature: monitoring page cache events
Date: Mon, 1 Aug 2016 07:07:37 -0700 [thread overview]
Message-ID: <579F57A9.5020708@intel.com> (raw)
In-Reply-To: <20160730173115.GA23083@thinkpad>
On 07/30/2016 10:31 AM, George Amvrosiadis wrote:
> Dave, I can produce a patch that adds the extra two tracepoints and exports
> all four tracepoint symbols. This would be a short patch that would just
> extend existing tracing functionality. What do you think?
Adding those tracepoints is probably useful. It's probably something we
need to have anyway as long as they don't cause too much code bloat or a
noticeable performance impact when they're off.
As for exporting symbols, that's not done until something is merged.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-08-01 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 3:47 [PATCH 0/3] new feature: monitoring page cache events George Amvrosiadis
2016-07-26 3:47 ` [PATCH 1/3] mm: support for duet hooks George Amvrosiadis
2016-07-26 3:47 ` [PATCH 2/3] mm/duet: syscall wiring George Amvrosiadis
2016-07-26 3:47 ` [PATCH 3/3] mm/duet: framework code George Amvrosiadis
2016-07-28 21:02 ` [PATCH 0/3] new feature: monitoring page cache events Dave Hansen
2016-07-29 3:47 ` George Amvrosiadis
2016-07-29 15:33 ` Dave Hansen
2016-07-30 17:31 ` George Amvrosiadis
2016-08-01 14:07 ` Dave Hansen [this message]
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=579F57A9.5020708@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=gamvrosi@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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).