From: Ingo Molnar <mingo@elte.hu>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] lockdep: shrink held_lock structure
Date: Sun, 14 Jan 2007 20:52:31 +0100 [thread overview]
Message-ID: <20070114195231.GA22911@elte.hu> (raw)
In-Reply-To: <20070114194217.GA20726@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> Subject: [patch] lockdep: shrink held_lock structure
> From: Dave Jones <davej@redhat.com>
>
> shrink the held_lock structure from 40 to 20 bytes. This shrinks struct
> task_struct from 3056 to 2464 bytes.
>
> [ From: Ingo Molnar <mingo@elte.hu>, shrunk hlock->class too. ]
doh - some buglet sneaked into the hlock->class_idx change ...
investigating it. Ignore this patch for now.
Ingo
prev parent reply other threads:[~2007-01-14 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 23:35 Shrink the held_lock struct by using bitfields Dave Jones
2007-01-02 23:38 ` Dave Jones
2007-01-14 18:45 ` Ingo Molnar
2007-01-14 19:42 ` [patch] lockdep: shrink held_lock structure Ingo Molnar
2007-01-14 19:52 ` Ingo Molnar [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=20070114195231.GA22911@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=davej@redhat.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