mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@transmeta.com>,
	David Howells <dhowells@cambridge.redhat.com>,
	Andrew Morton <andrewm@uow.edu.au>, Ben LaHaise <bcrl@redhat.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386 rw_semaphores fix
Date: Wed, 11 Apr 2001 02:13:18 +0200	[thread overview]
Message-ID: <20010411021318.A21221@khan.acc.umu.se> (raw)
In-Reply-To: <20010410220551.A24251@gruyere.muc.suse.de> <E14n6Be-0005Ir-00@the-village.bc.nu> <20010411020058.B28670@gruyere.muc.suse.de>
In-Reply-To: <20010411020058.B28670@gruyere.muc.suse.de>; from ak@suse.de on Wed, Apr 11, 2001 at 02:00:58AM +0200

On Wed, Apr 11, 2001 at 02:00:58AM +0200, Andi Kleen wrote:
> On Tue, Apr 10, 2001 at 11:00:31PM +0100, Alan Cox wrote:
> > > I guess 386 could live with an exception handler that emulates it.
> > 
> > 386 could use a simpler setup and is non SMP
> 
> The idea was to have a `generic' kernel that works on all architectures.
> If you drop 386 support much is better already.
>  
> > > (BTW an generic exception handler for CMPXCHG would also be very useful
> > > for glibc -- currently it has special checking code for 386 in its mutexes) 
> > > The 386 are so slow that nobody would probably notice a bit more slowness
> > > by a few exceptions.
> > 
> > Be serious. You can compile glibc without 386 support. Most vendors already
> > distribute 386/586 or 386/686 glibc sets.
> 
> Yes, and with CMPXCHG handler in the kernel it wouldn't be needed 
> (the other 686 optimizations like memcpy also work on 386) 

But the code would be much slower, and it's on 386's and similarly
slow beasts you need every cycle you can get, NOT on a Pentium IV.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-04-11  0:14 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AD0FD0F.9B0C47FD@uow.edu.au>
2001-04-09  3:08 ` rw_semaphores Linus Torvalds
2001-04-09  4:18   ` rw_semaphores Linus Torvalds
2001-04-09 13:55     ` rw_semaphores Ben LaHaise
2001-04-10  2:41 ` rw_semaphores Tachino Nobuhiro
2001-04-10  5:43   ` rw_semaphores Linus Torvalds
2001-04-10  7:47     ` rw_semaphores David Howells
2001-04-10 18:02       ` [PATCH] i386 rw_semaphores fix David Howells
2001-04-10 19:42         ` Linus Torvalds
2001-04-10 19:56           ` x86 cpu configuration (was: Re: [PATCH] i386 rw_semaphores fix) Jeff Garzik
2001-04-10 21:58             ` Alan Cox
2001-04-10 20:05           ` [PATCH] i386 rw_semaphores fix Andi Kleen
2001-04-10 20:16             ` Linus Torvalds
2001-04-10 22:00             ` Alan Cox
2001-04-11  0:00               ` Andi Kleen
2001-04-11  0:13                 ` David Weinehall [this message]
2001-04-11  0:20                   ` Andi Kleen
2001-04-11  0:56                     ` David Weinehall
2001-04-11  1:04                       ` Andi Kleen
2001-04-11 12:32                     ` Alan Cox
2001-04-11  0:55                   ` Linus Torvalds
2001-04-11  1:07                     ` Andi Kleen
2001-04-11  1:12                       ` Linus Torvalds
2001-04-11  1:23                         ` Andi Kleen
2001-04-11 12:36                           ` Alan Cox
2001-04-11 18:05                     ` H. Peter Anvin
2001-04-11 12:28                 ` Alan Cox
2001-04-11 18:06                   ` H. Peter Anvin
2001-04-11 22:06                     ` Alan Cox
2001-04-11 22:42                       ` H. Peter Anvin
2001-04-11 22:55                         ` Alan Cox
2001-04-10 21:57           ` Alan Cox
2001-04-11  0:40             ` Tim Wright
2001-04-11  7:38           ` David Howells
2001-04-11 12:24             ` Maciej W. Rozycki
2001-04-11 12:57           ` [PATCH] 2nd try: " David Howells
2001-04-11 16:37             ` [PATCH] 3rd " David Howells
2001-04-11 21:41               ` [PATCH] 4th " David Howells
2001-04-12 18:16                 ` Andrew Morton
2001-04-11 23:00               ` [PATCH] 3rd " Anton Blanchard
2001-04-12 15:06                 ` [PATCH] i386 rw_semaphores, general abstraction patch David Howells
2001-04-11 16:56         ` [PATCH] i386 rw_semaphores fix Andrew Morton
2001-04-11 17:36           ` David Howells
2001-04-11 18:41             ` Linus Torvalds
2001-04-11 21:27           ` David Howells
2001-04-16 14:39       ` rw_semaphores yodaiken
2001-04-16 14:56         ` rw_semaphores Alan Cox
2001-04-16 17:05         ` rw_semaphores Linus Torvalds
2001-04-16 17:34           ` rw_semaphores yodaiken
2001-04-16 17:26         ` rw_semaphores Andrew Morton
2001-04-10  6:33   ` rw_semaphores Tachino Nobuhiro

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=20010411021318.A21221@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrewm@uow.edu.au \
    --cc=bcrl@redhat.com \
    --cc=dhowells@cambridge.redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®