public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@gmail.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Lubos Lunak <l.lunak@suse.cz>, Dirk Mueller <dmueller@suse.de>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] the /proc/filecache interface
Date: Thu, 15 Jun 2006 09:03:16 +0800	[thread overview]
Message-ID: <350333369.20847@ustc.edu.cn> (raw)
Message-ID: <20060615010316.GB5013@mail.ustc.edu.cn> (raw)
In-Reply-To: <1150319970.12768.58.camel@dyn9047017100.beaverton.ibm.com>

On Wed, Jun 14, 2006 at 02:19:30PM -0700, Badari Pulavarty wrote:
> Interesting work. But I am worried that, this is getting over-designed.
> Lets go back to basics - what is the actual problem we are trying to
> solve here ? What are mininum requirements ? How does it help solve
> the problem ? Who & How one uses this ? Yes. I understand - these
> just provide stats on filecache, but we can provide all the nitty
> details - which are not really relevant or useful.
> 
> Don't get me wrong - I really need better understanding of whats there
> in pagecache. Infact, I need a better way to control how much filecache
> in pagecache. 
> 
> (BTW, I like your patch for "educational" purposes - but I am not
> sure how useful it is for practical purpose).

Badari,

Thanks for the comment. The interface does provides some more details
than I will actually need. The intention is to show the possibilities
in the first place, and trim down / expand a bit based on feedbacks.

For the GUI pre-caching stuffs I'm working on, the following features
will be essential ones:
        - file list view
                - sorted roughly on the first access time
                - the size/cached/dev/file attributes
        - page list view
                - the idx/len/state attributes
                - the referenced/active/mmap page flags

Thanks,
Wu

      reply	other threads:[~2006-06-15  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060612075130.GA5432@mail.ustc.edu.cn>
2006-06-12  7:51 ` [RFC] the /proc/filecache interface Fengguang Wu
2006-06-14 11:05 ` Pavel Machek
     [not found]   ` <20060614122934.GB6564@mail.ustc.edu.cn>
2006-06-14 12:29     ` Fengguang Wu
2006-06-14 15:38 ` Bernard Blackham
     [not found]   ` <20060615004034.GA5013@mail.ustc.edu.cn>
2006-06-15  0:40     ` Fengguang Wu
2006-06-15  2:05     ` Bernard Blackham
2006-06-14 21:19 ` Badari Pulavarty
     [not found]   ` <20060615010316.GB5013@mail.ustc.edu.cn>
2006-06-15  1:03     ` Fengguang Wu [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=350333369.20847@ustc.edu.cn \
    --to=fengguang.wu@gmail.com \
    --cc=akpm@osdl.org \
    --cc=dmueller@suse.de \
    --cc=l.lunak@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.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