From: Maneesh Soni <maneesh@in.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Dipankar Sarma <dipankar@in.ibm.com>,
"Martin J. Bligh" <mjbligh@us.ibm.com>,
Matt Mackall <mpm@selenic.com>,
Christian Borntraeger <CBORNTRA@de.ibm.com>
Subject: [RFC/T 0/6] sysfs backing store (with symlink)
Date: Wed, 4 Feb 2004 17:07:58 +0530 [thread overview]
Message-ID: <20040204113758.GA4234@in.ibm.com> (raw)
Hi All,
Please find following patches for sysfs-backing store. This version has
support for putting symlinks also on backing store. Earlier it has support
for text/binary attribute files.
http://marc.theaimsgroup.com/?l=linux-kernel&m=107269078726254&w=2
Apart from a few bug fixes, the main change in this version is for symlinks.
sysfs_create_link() now does not create dentry/inode for the link, but
allocates a sysfs_dirent and adds it the parent sysfs_dirent's s_children
list. dentry/inode for the link is created when the symlink is first looked up.
I request Martin and Mackall to _replace_ the old patch set with the
new one in their trees.
With this we save approx 75-80% of lowmem requirements of sysfs. Symlinks
support is needed for S390 linux people as they create lots of symlinks. I
have some numbers collected on S390 machine after creating 4096 ctc devices.
This created around 62433 sysfs entries. Backing store saves around 145 MB
of Lowmem when sysfs files are not in use.
---------------------------------------------------------------------------
Without sysfs backing store
# cat /proc/sys/fs/dentry-state
66733 4100 45 0 0 0
# grep LowFree /proc/meminfo
LowFree: 20984 kB
# grep dentry /proc/slabinfo; grep -w inode_cache /proc/slabinfo
dentry_cache 66750 66750 256 15 1 : tunables 120 60 8 : slabdata 4450 4450 0
inode_cache 62480 62480 768 5 1 : tunables 54 27 8 : slabdata 12496 12496 0
---------------------------------------------------------------------------
---------------------------------------------------------------------------
With sysfs backing store
# cat /proc/sys/fs/dentry-state
8783 155 45 0 0 0
# grep LowFree /proc/meminfo
LowFree: 166416 kB
# grep dentry /proc/slabinfo; grep -w inode_cache /proc/slabinfo
dentry_cache 8795 8880 256 15 1 : tunables 120 60 8 : slabdata 592 592 0
inode_cache 8495 8495 768 5 1 : tunables 54 27 8 : slabdata 1699 1699 0
**** Savings of around 145 MB of Lowmem *****
---------------------------------------------------------------------------
Thanks
Maneesh
--
Maneesh Soni
Linux Technology Center,
IBM Software Lab, Bangalore, India
email: maneesh@in.ibm.com
Phone: 91-80-5044999 Fax: 91-80-5268553
T/L : 9243696
next reply other threads:[~2004-02-04 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 11:37 Maneesh Soni [this message]
2004-02-04 11:38 ` [RFC/T 1/6] sysfs backing store (with symlink) Maneesh Soni
2004-02-04 11:39 ` [RFC/T 2/6] " Maneesh Soni
2004-02-04 11:40 ` [RFC/T 3/6] " Maneesh Soni
2004-02-04 11:40 ` [RFC/T 4/6] " Maneesh Soni
2004-02-04 11:41 ` [RFC/T 5/6] " Maneesh Soni
2004-02-04 11:41 ` [RFC/T 6/6] " Maneesh Soni
2004-02-05 19:59 ` [RFC/T 0/6] " Matt Mackall
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=20040204113758.GA4234@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=CBORNTRA@de.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=mpm@selenic.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox