WU Fengguang <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
