From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Ulrich Drepper <drepper@redhat.com>,
Paul Jackson <pj@sgi.com>, Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 0/6] lightweight robust futexes: -V4
Date: Tue, 21 Feb 2006 11:37:10 -0500 [thread overview]
Message-ID: <20060221163710.GX24295@devserv.devel.redhat.com> (raw)
In-Reply-To: <a36005b50602210826i567effabsd4b43da9804db86d@mail.gmail.com>
On Tue, Feb 21, 2006 at 08:26:05AM -0800, Ulrich Drepper wrote:
> > The `len' argument (or really revision of the structure if really needed)
> > can be encoded in the structure, as in:
> > struct robust_list_head {
> > struct robust_list list;
> > short robust_list_head_len; /* or robust_list_head_version ? */
> > short futex_offset;
> > struct robust_list __user *list_op_pending;
> > };
> > or with long futex_offset, but using say upper 8 bits of the field as
> > version or length.
>
> I know you want to save SPARC but this kind of overloading I don't
> really like. If you need special treatment of the futex value make
> this explicit and arch-dependent.
This had nothing to do with SPARC actually, I only wanted to avoid
passing two extra arguments to clone rather than one. But if you think
CLONE_CHILD_SETROBUST is unnecessary, so be it and the combined
set_tid_robust_address call can have tidptr, robustptr and robustlen
arguments.
Jakub
next prev parent reply other threads:[~2006-02-21 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 8:46 [patch 0/6] lightweight robust futexes: -V4 Ingo Molnar
2006-02-21 9:23 ` Jakub Jelinek
2006-02-21 16:26 ` Ulrich Drepper
2006-02-21 16:37 ` Jakub Jelinek [this message]
2006-02-23 5:01 ` Eric W. Biederman
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=20060221163710.GX24295@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=drepper@gmail.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--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.