All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
	linux-kernel@vger.kernel.org, jakub@redhat.com
Subject: Re: [PATCH] 2.6.16 - futex: small optimization (?)
Date: Fri, 31 Mar 2006 20:15:48 +0200	[thread overview]
Message-ID: <20060331181548.GA25053@elte.hu> (raw)
In-Reply-To: <442D41B1.1070005@tmr.com>


* Bill Davidsen <davidsen@tmr.com> wrote:

> >What are you suggesting here, that the implementation of 
> >FUTEX_WAKE_OP is "ignoring inefficiencies"? Please explain why and 
> >what you would do differently to solve that inefficiency.
>
> I am suggesting that "There are no such situations anymore in an 
> optimal userlevel implementation" is not the right approach to the 
> original post. What I would do differently is to evaluate the original 
> suggestion to see if it would in fact be more efficient. [...]

that's what we did a year ago for a similar futex rescheduling 
inefficiency, and came up with the FUTEX_WAKE_OP solution, which is now 
part of the kernel and is used by glibc. But we are all ears for 
alternative suggestions.

	Ingo

  reply	other threads:[~2006-03-31 18:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  7:37 [PATCH] 2.6.16 - futex: small optimization (?) Pierre PEIFFER
2006-03-28 10:05 ` Eric Dumazet
2006-03-28 15:02 ` Ulrich Drepper
2006-03-28 22:46   ` Bill Davidsen
2006-03-29 15:26     ` Ingo Molnar
2006-03-30 20:27       ` Bill Davidsen
2006-03-31  6:01         ` Ingo Molnar
2006-03-31 14:50           ` Bill Davidsen
2006-03-31 18:15             ` Ingo Molnar [this message]
2006-03-29 13:18   ` Pierre PEIFFER
2006-03-29 15:26     ` Eric Dumazet
2006-03-30 14:51       ` Pierre PEIFFER

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=20060331181548.GA25053@elte.hu \
    --to=mingo@elte.hu \
    --cc=davidsen@tmr.com \
    --cc=drepper@gmail.com \
    --cc=jakub@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 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.