All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: inode/dcache overhead of sysfs attribute files?
Date: Wed, 02 Jul 2003 19:48:11 -0400	[thread overview]
Message-ID: <3F036F3B.7030004@pobox.com> (raw)
In-Reply-To: <20030702215847.GA9973@kroah.com>

Has anybody looked into the inode and dcache overhead of all this stuff, 
which I assume is pinned into memory a la ramfs?

I wonder if sysfs attributes could be accessed via the extended 
attribute VFS API?  A file full of EA's can easily be considered a 
key-value database, or attribute-value in this case :)  The EA names and 
values need not pin a bunch of inodes and dcache entries, either.
(though viro may scream at my mention of EAs :))

	Jeff




  reply	other threads:[~2003-07-02 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 21:58 [RFC] add module reference counts to sysfs attribute files Greg KH
2003-07-02 23:48 ` Jeff Garzik [this message]
2003-07-02 23:57   ` inode/dcache overhead of sysfs attribute files? Greg KH

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=3F036F3B.7030004@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=greg@kroah.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.