Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Ariel Faigon <ariel@oz.engr.sgi.com>,
	Olivier Galibert <galibert@pobox.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: help offered
Date: Thu, 26 Nov 1998 06:28:37 -0600	[thread overview]
Message-ID: <19981126062837.A1134@uni-koblenz.de> (raw)
In-Reply-To: <199811252037.MAA37649@oz.engr.sgi.com>; from Ariel Faigon on Wed, Nov 25, 1998 at 12:37:36PM -0800

On Wed, Nov 25, 1998 at 12:37:36PM -0800, Ariel Faigon wrote:

> :Linux 2.1.* is very preemtible, even if there are  stil some things to
> :do.
> 
> Interesting.  Could you elaborate on:
> 
> 	0) What was changed in recent Linux kernels
> 	   to support preemtibility in kernel space?

I think people are confusing the terms reentrant and preemptible.

> 	1) Which "serious" (i.e not 'getpid') system calls are
> 	   now reentrant ?

The large majority of the ``small stuff'' is now reentrant, that means
signals, interrupts, stuff like getpid.  Many subsystems or structures are
nowadays protected by there own locks and no longer by the big evil
lock-everything kernel lock.

> 	2) What still remains to be done so Linux can really
> 	   scale before it gets bottlenecked by kernel locks ?

The big ones which still need a lot of work are

 - VFS and lower layers are protected by the big kernel lock.
 - bottom half handlers run on only one CPU.
 - socket code is protected by the big kernel lock

It's 2.3 work, don't expect it to happen any day soon.  If you're
interested in more details, grep the kernel for lock_kernel / unlock_kernel.

  Ralf

  parent reply	other threads:[~1998-11-26 12:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-24 12:27 help offered Torbjörn Gannholm
1998-11-24 20:33 ` Ariel Faigon
1998-11-25 19:49   ` Olivier Galibert
1998-11-25 19:57     ` John E. Schimmel
1998-11-25 19:57       ` John E. Schimmel
1998-11-25 20:11     ` Jeffrey Watts
1998-11-25 20:43       ` Greg Chesson
1998-11-25 20:37     ` Ariel Faigon
1998-11-25 20:37       ` Ariel Faigon
1998-11-25 20:51       ` pjlahaie
1998-11-25 21:18         ` William J. Earl
1998-11-25 21:18           ` William J. Earl
1998-11-25 21:24         ` Greg Chesson
1998-11-25 21:24           ` Greg Chesson
1998-11-25 21:38           ` pjlahaie
1998-11-25 21:57             ` Greg Chesson
1998-11-25 21:57               ` Greg Chesson
1998-11-25 22:09               ` pjlahaie
1998-11-25 22:57                 ` Greg Chesson
1998-11-25 22:57                   ` Greg Chesson
1998-11-25 22:08             ` William J. Earl
1998-11-25 22:08               ` William J. Earl
1998-11-25 22:13         ` Alex Kozlov
1998-11-25 22:15           ` pjlahaie
1998-11-25 22:25           ` William J. Earl
1998-11-25 22:25             ` William J. Earl
1998-11-25 21:46       ` Alan Cox
1998-11-25 21:04         ` Greg Chesson
1998-11-25 21:04           ` Greg Chesson
1998-11-26 12:28       ` ralf [this message]
     [not found]         ` <19981126085407.A2201@uni-koblenz.de>
1998-11-27 22:59           ` Olivier Galibert
1998-11-28  2:45             ` ralf
1998-11-26 22:17       ` Miguel de Icaza
1998-11-25 20:56     ` Greg Chesson
1998-11-25 21:12       ` Olivier Galibert

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=19981126062837.A1134@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=ariel@oz.engr.sgi.com \
    --cc=galibert@pobox.com \
    --cc=linux@cthulhu.engr.sgi.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