From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: make proc entry's len "unsigned int"
Date: Tue, 4 Jan 2011 16:51:59 -0800 [thread overview]
Message-ID: <20110104165159.49c257b7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101126211033.GA14339@core2.telecom.by>
On Fri, 26 Nov 2010 23:10:33 +0200
Alexey Dobriyan <adobriyan@gmail.com> wrote:
> Space is not really conserved, because of natural alignment for the next field.
>
> ...
>
> --- a/fs/proc/generic.c
> +++ b/fs/proc/generic.c
> @@ -28,7 +28,7 @@
>
> DEFINE_SPINLOCK(proc_subdir_lock);
>
> -static int proc_match(int len, const char *name, struct proc_dir_entry *de)
> +static int proc_match(unsigned int len, const char *name, struct proc_dir_entry *de)
> {
> if (de->namelen != len)
> return 0;
> @@ -303,7 +303,7 @@ static int __xlate_proc_name(const char *name, struct proc_dir_entry **ret,
> {
> const char *cp = name, *next;
> struct proc_dir_entry *de;
> - int len;
> + unsigned int len;
>
> de = *ret;
> if (!de)
> @@ -605,7 +605,7 @@ static struct proc_dir_entry *__proc_create(struct proc_dir_entry **parent,
> {
> struct proc_dir_entry *ent = NULL;
> const char *fn = name;
> - int len;
> + unsigned int len;
>
> /* make sure name is valid */
> if (!name || !strlen(name)) goto out;
> @@ -794,7 +794,7 @@ void remove_proc_entry(const char *name, struct proc_dir_entry *parent)
> struct proc_dir_entry **p;
> struct proc_dir_entry *de = NULL;
> const char *fn = name;
> - int len;
> + unsigned int len;
>
> spin_lock(&proc_subdir_lock);
> if (__xlate_proc_name(name, &parent, &fn) != 0) {
> --- a/include/linux/proc_fs.h
> +++ b/include/linux/proc_fs.h
> @@ -50,7 +50,7 @@ typedef int (write_proc_t)(struct file *file, const char __user *buffer,
>
> struct proc_dir_entry {
> unsigned int low_ino;
> - unsigned short namelen;
> + unsigned int namelen;
> const char *name;
> mode_t mode;
> nlink_t nlink;
Well, if we _can_ save some space here then the returns would be
appreciable.
akpm:/home/akpm# find /proc | wc -l
95543
(wtf?)
akpm:/home/akpm# find /proc/[0-9]* | wc -l
94212
(oh.)
Do all of those things have a proc_dir_entry? IIRC we changed things
so they're somewhat allocate-on-demand.
next prev parent reply other threads:[~2011-01-05 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 21:10 [PATCH] proc: make proc entry's len "unsigned int" Alexey Dobriyan
2010-11-26 23:58 ` Joe Perches
2011-01-05 0:51 ` Andrew Morton [this message]
2011-01-05 8:45 ` Alexey Dobriyan
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=20110104165159.49c257b7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.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