All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "Andi Kleen" <andi@firstfloor.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jens Axboe" <axboe@kernel.dk>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Rik van Riel" <riel@redhat.com>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [PATCH] proc: show readahead state in fdinfo
Date: Thu, 15 Dec 2011 10:49:22 +0100	[thread overview]
Message-ID: <20111215094922.GA29981@elte.hu> (raw)
In-Reply-To: <20111215085540.GA23966@localhost>


* Wu Fengguang <fengguang.wu@intel.com> wrote:

> On Wed, Nov 30, 2011 at 01:57:43AM +0800, Andi Kleen wrote:
> > On Tue, Nov 29, 2011 at 09:09:03PM +0800, Wu Fengguang wrote:
> > > Record the readahead pattern in ra->pattern and extend the ra_submit()
> > > parameters, to be used by the next readahead tracing/stats patches.
> > 
> > I like this, could it be exported it a bit more formally in /proc for 
> > each file descriptor?
> 
> How about this?
> ---
> Subject: proc: show readahead state in fdinfo
> Date: Thu Dec 15 14:35:56 CST 2011
> 
> Append three readahead states to /proc/<PID>/fdinfo/<FD>:

Not a very good idea - please keep debug info under /debug as 
much as possible (as your original series did), instead of 
creating an ad-hoc insta-ABI in /proc.

In the long run we'd really like to retrieve such kind of 
information not even via ad-hoc exported info in /debug but via 
the standard event facilities: the tracepoints, if they are 
versatile enough, could be used to collect these stats and more.

Thanks,

	Ingo

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "Andi Kleen" <andi@firstfloor.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jens Axboe" <axboe@kernel.dk>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Rik van Riel" <riel@redhat.com>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [PATCH] proc: show readahead state in fdinfo
Date: Thu, 15 Dec 2011 10:49:22 +0100	[thread overview]
Message-ID: <20111215094922.GA29981@elte.hu> (raw)
In-Reply-To: <20111215085540.GA23966@localhost>


* Wu Fengguang <fengguang.wu@intel.com> wrote:

> On Wed, Nov 30, 2011 at 01:57:43AM +0800, Andi Kleen wrote:
> > On Tue, Nov 29, 2011 at 09:09:03PM +0800, Wu Fengguang wrote:
> > > Record the readahead pattern in ra->pattern and extend the ra_submit()
> > > parameters, to be used by the next readahead tracing/stats patches.
> > 
> > I like this, could it be exported it a bit more formally in /proc for 
> > each file descriptor?
> 
> How about this?
> ---
> Subject: proc: show readahead state in fdinfo
> Date: Thu Dec 15 14:35:56 CST 2011
> 
> Append three readahead states to /proc/<PID>/fdinfo/<FD>:

Not a very good idea - please keep debug info under /debug as 
much as possible (as your original series did), instead of 
creating an ad-hoc insta-ABI in /proc.

In the long run we'd really like to retrieve such kind of 
information not even via ad-hoc exported info in /debug but via 
the standard event facilities: the tracepoints, if they are 
versatile enough, could be used to collect these stats and more.

Thanks,

	Ingo

  reply	other threads:[~2011-12-15  9:49 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 13:09 [PATCH 0/9] readahead stats/tracing, backwards prefetching and more (v2) Wu Fengguang
2011-11-29 13:09 ` Wu Fengguang
2011-11-29 13:09 ` [PATCH 1/9] block: limit default readahead size for small devices Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09 ` [PATCH 2/9] readahead: snap readahead request to EOF Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 14:29   ` Jan Kara
2011-11-29 14:29     ` Jan Kara
2011-11-30  1:06     ` Wu Fengguang
2011-11-30  1:06       ` Wu Fengguang
2011-11-30 11:37       ` Jan Kara
2011-11-30 11:37         ` Jan Kara
2011-11-30 12:06         ` Wu Fengguang
2011-11-30 12:06           ` Wu Fengguang
2011-11-29 13:09 ` [PATCH 3/9] readahead: record readahead patterns Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 14:40   ` Jan Kara
2011-11-29 14:40     ` Jan Kara
2011-11-29 17:57   ` Andi Kleen
2011-11-29 17:57     ` Andi Kleen
2011-11-30  1:18     ` Wu Fengguang
2011-11-30  1:18       ` Wu Fengguang
2011-12-15  8:55     ` [PATCH] proc: show readahead state in fdinfo Wu Fengguang
2011-12-15  8:55       ` Wu Fengguang
2011-12-15  9:49       ` Ingo Molnar [this message]
2011-12-15  9:49         ` Ingo Molnar
2011-11-29 13:09 ` [PATCH 4/9] readahead: tag mmap page fault call sites Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 14:41   ` Jan Kara
2011-11-29 14:41     ` Jan Kara
2011-11-29 13:09 ` [PATCH 5/9] readahead: tag metadata " Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 14:45   ` Jan Kara
2011-11-29 14:45     ` Jan Kara
2011-11-29 13:09 ` [PATCH 6/9] readahead: add /debug/readahead/stats Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 15:21   ` Jan Kara
2011-11-29 15:21     ` Jan Kara
2011-11-30  0:44     ` Wu Fengguang
2011-11-30  0:44       ` Wu Fengguang
2011-12-14  6:36     ` Wu Fengguang
2011-12-14  6:36       ` Wu Fengguang
2011-12-19 16:32       ` Jan Kara
2011-12-19 16:32         ` Jan Kara
2011-12-21  1:29         ` Wu Fengguang
2011-12-21  1:29           ` Wu Fengguang
2011-12-21  4:06           ` Dave Chinner
2011-12-21  4:06             ` Dave Chinner
2011-12-23  3:33             ` Wu Fengguang
2011-12-23  3:33               ` Wu Fengguang
2011-12-23 11:16               ` Jan Kara
2011-12-23 11:16                 ` Jan Kara
2011-11-29 13:09 ` [PATCH 7/9] readahead: add vfs/readahead tracing event Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 15:22   ` Jan Kara
2011-11-29 15:22     ` Jan Kara
2011-11-30  0:42     ` Wu Fengguang
2011-11-30  0:42       ` Wu Fengguang
2011-11-30 11:44       ` Jan Kara
2011-11-30 11:44         ` Jan Kara
2011-11-30 12:06         ` Wu Fengguang
2011-11-30 12:06           ` Wu Fengguang
2011-12-06 15:30   ` Christoph Hellwig
2011-12-06 15:30     ` Christoph Hellwig
2011-12-07  9:18     ` Wu Fengguang
2011-12-07  9:18       ` Wu Fengguang
2011-12-08  9:03     ` [PATCH] writeback: show writeback reason with __print_symbolic Wu Fengguang
2011-12-08  9:03       ` Wu Fengguang
2011-11-29 13:09 ` [PATCH 8/9] readahead: basic support for backwards prefetching Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 15:35   ` Jan Kara
2011-11-29 15:35     ` Jan Kara
2011-11-29 16:37     ` Pádraig Brady
2011-11-29 16:37       ` Pádraig Brady
2011-11-29 16:37       ` Pádraig Brady
2011-11-30  0:24       ` Wu Fengguang
2011-11-30  0:24         ` Wu Fengguang
2011-11-30  0:24         ` Wu Fengguang
2011-11-30  0:37     ` Wu Fengguang
2011-11-30  0:37       ` Wu Fengguang
2011-11-30 11:21       ` Jan Kara
2011-11-30 11:21         ` Jan Kara
2011-11-29 13:09 ` [PATCH 9/9] readahead: dont do start-of-file readahead after lseek() Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang
2011-11-29 13:09   ` Wu Fengguang

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=20111215094922.GA29981@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=axboe@kernel.dk \
    --cc=fengguang.wu@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.