From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH 0/4] sysfs: Reduce the size of sysfs_dirent
Date: Sun, 08 Jan 2012 10:15:31 -0800 [thread overview]
Message-ID: <m1wr9283i4.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20120108175645.GC29499@suse.de> (Greg KH's message of "Sun, 8 Jan 2012 09:56:45 -0800")
Greg KH <gregkh@suse.de> writes:
> On Tue, Jan 03, 2012 at 09:43:47PM -0800, Eric W. Biederman wrote:
>> ebiederm@xmission.com (Eric W. Biederman) writes:
>>
>> > After throwing rb_trees at the problem sysfs_dirent increased in size by
>> > 6 pointers, or 48 bytes. Since the point of having struct
>> > sysfs_dirent is to keep the size down increasing in size that much seems
>> > unfortunate.
>> >
>> > The following patches attack this problem and if I have counted right
>> > reduce the size of sysfs_dirent by 4 pointers on 64bit. Not quite
>> > where we were but reducing sysfs_dirent by 32bytes to 104 bytes is
>> > an improvement.
>>
>> Greg did you see these patches for reducing the sysfs memory size
>> regression in 3.2?
>
> Ok, due to the holidays, these ended up missing the 3.3 merge window,
> I'll queue them up for 3.4.
Thanks.
Eric
prev parent reply other threads:[~2012-01-08 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 4:03 Eric W. Biederman
2011-12-19 4:05 ` [PATCH 1/4] sysfs: Add s_hash to sysfs_dirent and order directory entries by hash Eric W. Biederman
2011-12-19 4:07 ` [PATCH 2/4] sysfs: Reduce s_flags to an unsinged short so it packs well with s_mode Eric W. Biederman
2011-12-19 4:08 ` [PATCH 3/4] sysfs: Store the sysfs inode in an unsigned int Eric W. Biederman
2011-12-19 4:09 ` [PATCH 4/4] sysfs: Kill nlink counting Eric W. Biederman
2012-01-04 5:43 ` [PATCH 0/4] sysfs: Reduce the size of sysfs_dirent Eric W. Biederman
2012-01-08 17:56 ` Greg KH
2012-01-08 18:15 ` Eric W. Biederman [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=m1wr9283i4.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=tj@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
Powered by JetHome