From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Patch(2.5.54): devfs shrink - integration candidate
Date: 8 Jan 2003 10:55:49 -0800 [thread overview]
Message-ID: <avhs7l$qnc$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030105203725.A10808@adam.yggdrasil.com
Followup to: <20030105203725.A10808@adam.yggdrasil.com>
By author: "Adam J. Richter" <adam@yggdrasil.com>
In newsgroup: linux.dev.kernel
>
> This patch reduces include/linux/devfs*.h and fs/devfs from
> 3655 lines to 1239, a reduction of 2450 lines, nearly a factor three.
> That may not be as impressive as the original 5X reduction, but that
> is mostly because I've restored a bunch of functionality that I hope
> to eliminate in the future.
>
Do we have any idea what the impact of this is on runtime data size?
I seem to remember devfs playing lots of tricks to reduce its working
set. If this code size reduction ends up pinning large data
structures like dentries and inodes which wouldn't otherwise have been
pinned, this could be a significant lose.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2003-01-08 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030105201413.A10685@adam.yggdrasil.com>
2003-01-06 4:37 ` Patch(2.5.54): devfs shrink - integration candidate Adam J. Richter
2003-01-06 4:56 ` Andi Kleen
2003-01-06 9:57 ` Andrew Walrond
2003-01-06 10:12 ` John Bradford
2003-01-06 5:04 ` Andrew Morton
2003-01-08 18:55 ` H. Peter Anvin [this message]
2003-01-06 5:14 Adam J. Richter
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='avhs7l$qnc$1@cesium.transmeta.com' \
--to=hpa@zytor.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