All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	Patrick Mochel <mochel@osdl.org>,
	Christian Borntraeger <CBORNTRA@de.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [RFC 0/5] Backing Store for sysfs (Overhauled)
Date: Wed, 12 Nov 2003 08:00:15 -0800	[thread overview]
Message-ID: <20031112160015.GA28684@kroah.com> (raw)
In-Reply-To: <20031112122344.GD14580@in.ibm.com>

On Wed, Nov 12, 2003 at 05:53:44PM +0530, Maneesh Soni wrote:
> 
> The concept is still the same that in this prototype also we create dentry and 
> inode on the fly when they are first looked up. This is done for both leaf or 
> non-leaf dentries. The generic nature of sysfs_dirent makes it easy to do for 
> both leaf or non-leaf dentries. 

What happens once a dentry and inode is created?  Is there any way for
them to be forced out, or do they stay around in memory forever?

thanks,

greg k-h

  parent reply	other threads:[~2003-11-12 16:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 12:23 [RFC 0/5] Backing Store for sysfs (Overhauled) Maneesh Soni
2003-11-12 12:25 ` [RFC 1/5] sysfs-backing-store.patch Maneesh Soni
2003-11-12 12:25   ` [RFC 2/5] sysfs-dir.patch Maneesh Soni
2003-11-12 12:25     ` [RFC 3/5] sysfs-file.patch Maneesh Soni
2003-11-12 12:26       ` [RFC 4/5] sysfs-attr_group.patch Maneesh Soni
2003-11-12 12:26         ` [RFC 5/5] sysfs-symlink.patch Maneesh Soni
2003-11-12 14:39     ` [RFC 2/5] sysfs-dir.patch viro
2003-11-12 16:00 ` Greg KH [this message]
2003-11-12 16:27   ` [RFC 0/5] Backing Store for sysfs (Overhauled) Dipankar Sarma
2003-11-12 16:39     ` Greg KH
2003-11-13 19:34 ` Patrick Mochel
2003-11-13 19:55   ` Dipankar Sarma

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=20031112160015.GA28684@kroah.com \
    --to=greg@kroah.com \
    --cc=CBORNTRA@de.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=mochel@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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.