From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inode/dcache overhead of sysfs attribute files?
Date: Wed, 2 Jul 2003 16:57:43 -0700 [thread overview]
Message-ID: <20030702235743.GA10868@kroah.com> (raw)
In-Reply-To: <3F036F3B.7030004@pobox.com>
On Wed, Jul 02, 2003 at 07:48:11PM -0400, Jeff Garzik wrote:
> Has anybody looked into the inode and dcache overhead of all this stuff,
> which I assume is pinned into memory a la ramfs?
Yes, there were some numbers in an old thread about 2000 scsi disks.
> 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 :))
Don't know, that could be one way. I think wli and shaggy were working
on something along these lines, but haven't heard from them in a long
time about it.
thanks,
greg k-h
prev parent reply other threads:[~2003-07-03 16:06 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 ` inode/dcache overhead of sysfs attribute files? Jeff Garzik
2003-07-02 23:57 ` Greg KH [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=20030702235743.GA10868@kroah.com \
--to=greg@kroah.com \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox