mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] unify semaphore implementations
Date: Thu, 28 Apr 2005 20:42:38 -0400	[thread overview]
Message-ID: <1114735358.9738.36.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20050428234005.A19778@flint.arm.linux.org.uk>

to den 28.04.2005 Klokka 23:40 (+0100) skreiv Russell King:
> On Thu, Apr 28, 2005 at 02:29:26PM -0400, Benjamin LaHaise wrote:
> > Please review the following series of patches for unifying the 
> > semaphore implementation across all architectures (not posted as 
> > they're about 350K), as they have only been tested on x86-64.  The 
> > code generated is functionally identical to the earlier i386 
> > variant, but since gcc has no way of taking condition codes as 
> > results, there are two additional instructions inserted from the 
> > use of generic atomic operations.  All told the >6000 lines of code 
> > deleted makes for a much easier job for subsequent patches changing 
> > semaphore functionality.  Cheers,
> 
> I'm not sure why we're doing this, apart from a desire to unify stuff.

It started from a desire to extend the existing implementations to
support new features such as asynchronous notification. Currently that
sort of thing is impossible unless your developer-super-powers include
the ability to herd 24 different subsystem maintainers into working
together on a solution.

In other words, the main drive is the desire to make it maintainable.

Cheers,
  Trond
-- 
Trond Myklebust <trond.myklebust@fys.uio.no>


  reply	other threads:[~2005-04-29  0:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 18:29 Benjamin LaHaise
2005-04-28 18:48 ` James Bottomley
2005-04-28 18:59   ` Benjamin LaHaise
2005-04-28 18:53     ` David S. Miller
2005-04-28 22:40 ` Russell King
2005-04-29  0:42   ` Trond Myklebust [this message]
2005-04-29  1:26     ` Paul Mackerras
2005-04-28 22:54 ` David Howells
2005-04-29  0:44 ` Paul Mackerras
2005-04-29  5:33   ` Richard Henderson
2005-04-29 14:14   ` Benjamin LaHaise
2005-04-29 15:42     ` Trond Myklebust
2005-04-30  1:45       ` Paul Mackerras
2005-04-30  5:13         ` Paul Mackerras
2005-04-30 16:40         ` Trond Myklebust
2005-04-30  1:49     ` Paul Mackerras
2005-04-30 16:50       ` Trond Myklebust

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=1114735358.9738.36.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=bcrl@kvack.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®