From: Dipankar Sarma <dipankar@in.ibm.com>
To: Christoph Hellwig <hch@infradead.org>,
Ravikiran G Thirumalai <kiran@in.ibm.com>,
Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1 of 2] Scalable statistics counters
Date: Tue, 13 Aug 2002 01:35:46 +0530 [thread overview]
Message-ID: <20020813013546.A7819@in.ibm.com> (raw)
In-Reply-To: <20020812144605.A4595@infradead.org>; from hch@infradead.org on Mon, Aug 12, 2002 at 02:46:05PM +0100
On Mon, Aug 12, 2002 at 02:46:05PM +0100, Christoph Hellwig wrote:
> On Mon, Aug 12, 2002 at 06:35:24PM +0530, Ravikiran G Thirumalai wrote:
> > Hi Andrew,
> > Here is the new statctr patch with some of the changes suggested by Christoph.
> > Do you think the foll patch is ready to get into the mainline kernel now?
> > If so, will you forward this to Linus or shall I send the patch to him?
> > The following patch works on 2.5.31. I will be mailing out the 2.5.31
> > version of Dipankar's kmalloc_percpu dynamic memory allocator in a separate
> > mail (since statctrs depend on them ).
>
> But you ignored the most important suggestion. Using proc_calc_metrics()
> in new code is a mistake. It's a sign you want to use the seq_file
> interface. And exporting it outside proc_misc.c is an even bigger mistake.
Christoph,
Suppose I use seq_file interface and not put all statctrs in one /proc
file, how do I associate the statctr data structure with the /proc
inode ? IOW, how do I quickly get the statctr_pentry corresponding to the
counter in statctr_open() ?
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-08-12 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 13:05 [patch 1 of 2] Scalable statistics counters Ravikiran G Thirumalai
2002-08-12 13:46 ` Christoph Hellwig
2002-08-12 20:05 ` Dipankar Sarma [this message]
2002-08-12 20:09 ` Christoph Hellwig
2002-08-13 5:37 ` Dipankar Sarma
2002-08-13 13:29 ` Ravikiran G Thirumalai
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=20020813013546.A7819@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@zip.com.au \
--cc=hch@infradead.org \
--cc=kiran@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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.