All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: Dipankar Sarma <dipankar@in.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	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 18:59:21 +0530	[thread overview]
Message-ID: <20020813185921.F27366@in.ibm.com> (raw)
In-Reply-To: <20020813110725.A10332@in.ibm.com>; from dipankar@in.ibm.com on Tue, Aug 13, 2002 at 11:07:25AM +0530

On Tue, Aug 13, 2002 at 11:07:25AM +0530, Dipankar Sarma wrote:
> ... 
> Yes, that I learnt by looking at mounts_open(), the problem is how
> do I get the statctr_pentry (or statctr_group if you like) in
> the open method ? It seems to me that in order to do this, we
> need the following -
> 
> 1. An exported wrapper create_statctr_entry() around 
>    create_seq_entry() code that sticks the statctr_group pointer into
>    proc_entry->data.
> 2. Some way to get the proc entry from the inode in statctr_open()
>    and stick it to seq_file->private for seq_file methods to use.
> 
> Is this understanding correct or is there a better and simpler
> way to do this ?
>

Christoph,
I have used the above mentioned method now, alongwith the PDE macro to get
the proc_dir_entry from the inode.  I'll post the patch after testing it..

Thanks,
Kiran

      reply	other threads:[~2002-08-13 13:28 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
2002-08-12 20:09     ` Christoph Hellwig
2002-08-13  5:37       ` Dipankar Sarma
2002-08-13 13:29         ` 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=20020813185921.F27366@in.ibm.com \
    --to=kiran@in.ibm.com \
    --cc=akpm@zip.com.au \
    --cc=dipankar@in.ibm.com \
    --cc=hch@infradead.org \
    --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.