All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@zip.com.au>,
	Rik van Riel <riel@conectiva.com.br>,
	lse <lse-tech@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] [patch] Scalable statistics counters with /proc reporting
Date: Thu, 8 Aug 2002 15:09:57 +0530	[thread overview]
Message-ID: <20020808150957.A21873@in.ibm.com> (raw)
In-Reply-To: <20020807100216.A27321@infradead.org>; from hch@infradead.org on Wed, Aug 07, 2002 at 10:02:16AM +0100

On Wed, Aug 07, 2002 at 10:02:16AM +0100, Christoph Hellwig wrote:
>...
> What about a general s/_proc//g for the API?

Sure ...I was initially thinking of something like statctr_pentry,
but then thought statctr_proc_entry would be explicit although lengthy.

> 
> For statctr_init the flags argument would much better be named gfp_mask,

I'll do that. I was just following the same conventions as kmalloc and
kmem_cache_alloc; but gfp_mask is much better; thanx.

> the val argument should be removed and the counter initialized to zero
> by default - that's 90% of the uses..

Yup, I'll do this too.

> 
> Also the /proc-based implementation is really ugly.  It should be moved
> over to the seq_file interface at least, a simple ramfs-style own
> filesystem ("stats" filesystem type) would be the cleanest solution.

If I want to create difft proc files for difft groups of statctrs like 
say /proc/statistics/vmstats, /proc/statistics/netstats etc., dynamically,
using seq_file implementation might be not very neat...I have to 
confess I don't know much about seq_file interfaces....so pls correct
me if I am missing something......I just looked at them after your pointer. 

We wanted to keep things simple right now ... IMHO a custom file system 
right now might be complicating the patch.....maybe later when there are many 
users of statctrs 8-) ...

Thanks,
Kiran

      parent reply	other threads:[~2002-08-08  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07  8:52 [patch] Scalable statistics counters with /proc reporting Ravikiran G Thirumalai
2002-08-07  9:02 ` [Lse-tech] " Christoph Hellwig
2002-08-07 19:02   ` Andrew Morton
2002-08-08  4:41     ` Ravikiran G Thirumalai
2002-08-08  9:39   ` Ravikiran G Thirumalai [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=20020808150957.A21873@in.ibm.com \
    --to=kiran@in.ibm.com \
    --cc=akpm@zip.com.au \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=riel@conectiva.com.br \
    /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.