From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Ulrich Drepper <drepper@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>
Subject: [patch 0/5] lightweight robust futexes: -V2
Date: Wed, 15 Feb 2006 23:56:27 +0100 [thread overview]
Message-ID: <20060215225627.GA5599@elte.hu> (raw)
This is release -V2 of the "lightweight robust futexes" patchset.
The patchset can also be downloaded from:
http://redhat.com/~mingo/lightweight-robust-futexes/
one detail i forgot to mention before is the .text effect of the
feature:
text data bss dec hex filename
4698410 983432 798248 6480090 62e0da vmlinux.orig
4700692 983504 798248 6482444 62ea0c vmlinux.vma-based +2282 bytes
4698941 983540 798248 6480729 62e359 vmlinux.list-based +531 bytes
so we can get a more complete solution for a fourth of the .text size.
Changes since -V1:
- fixed FUTEX=n build errors (found by Andrew Morton)
- fixed patch ordering and other dependencies, so that at every step,
the kernel builds and boots fine with FUTEX=y and FUTEX=n.
(found by Andrew Morton)
Ingo
reply other threads:[~2006-02-15 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060215225627.GA5599@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.