mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: WU Fengguang <wfg@mail.ustc.edu.cn>
Cc: joern@wohnheim.fh-wedel.de, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] Adaptive read-ahead v4
Date: Mon, 17 Oct 2005 20:31:37 -0700	[thread overview]
Message-ID: <20051017203137.05350739.akpm@osdl.org> (raw)
In-Reply-To: <20051018025806.GA3963@mail.ustc.edu.cn>

WU Fengguang <wfg@mail.ustc.edu.cn> wrote:
>
> ...
> > > +	unsigned long pgra_backward;
> > > +	unsigned long pgra_backward_hit;
> > > +	unsigned long pgra_backward_eof;
> > > +
> > > +	unsigned long ra_random;	/* read-ahead on seek-and-read-pages */
> > > +	unsigned long ra_random_return;
> > > +	unsigned long ra_random_eof;
> > > +	unsigned long pgra_random;
> > > +	unsigned long pgra_random_hit;
> > > +	unsigned long pgra_random_eof;
> > > +
> > >  };
> > 
> > Without actually understanding what you're doing, wouldn't a struct
> > for all those groups make sense?  I bet it can simplify the actual
> > code as well.
> Yeah, I did not expect the structure to grow so large.

All that stuff shouldn't remain there long-term.

> It should be better to create a stand alone struct and create a
> dedicated entry in /proc/. The data would be a nice hint for
> administrators who care the performance.

You should treat such informaton as a development aid, really.  People are
very unlikely to look at it in real life.


  reply	other threads:[~2005-10-18  3:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 17:47 WU Fengguang
2005-10-17 17:30 ` Jörn Engel
2005-10-18  2:58   ` WU Fengguang
2005-10-18  3:31     ` Andrew Morton [this message]
2005-10-18 11:10       ` WU Fengguang
2005-10-20 15:14       ` Ingo Oeser
2005-10-21  6:42         ` 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=20051017203137.05350739.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=wfg@mail.ustc.edu.cn \
    /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

all inboxes | Powered by JetHome®