mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: mingo@elte.hu
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Matthew Kirkwood <matthew@hairy.beasts.org>,
	Benjamin LaHaise <bcrl@redhat.com>,
	David Axmark <david@mysql.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Lightweight userspace semaphores...
Date: Mon, 25 Feb 2002 10:29:39 +1100	[thread overview]
Message-ID: <E16f85L-0005QM-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Sat, 23 Feb 2002 16:03:14 BST." <Pine.LNX.4.33.0202231551300.4173-100000@localhost.localdomain>

In message <Pine.LNX.4.33.0202231551300.4173-100000@localhost.localdomain> you 
write:
> 
> On Sat, 23 Feb 2002, Rusty Russell wrote:
> 
> > 1) Interface is: open /dev/usem, pread, pwrite.
> 
> i like the patch, but the interface is ugly IMO. Why not new syscalls? I
> think these lightweight semaphores will become an important part of Linux,
> so having their own syscall entries is the most correct interface,
> something like:
> 
>   sys_sem_create()
>   sys_sem_destroy()

There is no create and destroy (init is purely userspace).  There is
"this is a semapore: up it".  This is a feature.

>   sys_sem_down()
>   sys_sem_up()
> 
> /dev/usem is such an ... ioctl()-ish approach. It's a scalability problem
> as well: read()/write() has (or can have) some implicit locking that is
> imposed on the usem interface as well.

Agreed with implicit locking: good catch.  Disagree with neatness: I
like finding out in advance that there's no fast semaphore support.

> Plus sys_sem_create() should do some proper resource limit management,
> pinning down an unlimited number of pages is bad.

Since pages are pinned "on demand" and a process can only do one
syscall at a time, the maximum number of pinned pages per process ==
2.  Which is fine.

Will do syscall version, and see if I can actually get it to beat
fcntl locking on reasonable benchmarks (ie. tdbtorture).

Cheers!
Rusty.
PS.  Nomenclature: my fiance suggested FUS (Fast Userspace
     Semaphores), and I am legally obliged to agree.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2002-02-24 23:30 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  3:47 Rusty Russell
2002-02-23 15:03 ` Ingo Molnar
2002-02-23 18:20   ` Linus Torvalds
2002-02-23 18:28     ` Larry McVoy
2002-02-23 20:31       ` Ingo Molnar
2002-02-23 21:22       ` Alan Cox
2002-02-26 16:09     ` Hubertus Franke
2002-02-24 23:29   ` Rusty Russell [this message]
2002-02-24 23:48     ` Linus Torvalds
2002-02-25  1:10       ` Rusty Russell
2002-02-25  1:23         ` Linus Torvalds
2002-02-25 13:14           ` Alan Cox
2002-02-25 16:11             ` Linus Torvalds
2002-02-25 16:39               ` Alan Cox
2002-02-25 16:32                 ` Benjamin LaHaise
2002-02-25 17:42                   ` Alan Cox
2002-02-25 18:23                   ` Hubertus Franke
2002-02-25 20:57                     ` Hubertus Franke
2002-02-25 17:06                 ` Linus Torvalds
2002-02-25 17:31                   ` Alan Cox
2002-02-25 17:20                     ` Linus Torvalds
2002-02-25 17:50                       ` Alan Cox
2002-02-25 17:44                         ` Linus Torvalds
2002-02-25 18:06                           ` Alan Cox
2002-02-25 19:31                             ` Linus Torvalds
2002-02-24  4:57                               ` Daniel Phillips
2002-02-25 19:51                             ` Hubertus Franke
2002-02-26 12:15                       ` [PATCH] 2.5.5 IDE clean 14 Martin Dalecki
2002-02-26 21:49                         ` Keith Owens
2002-02-27 10:08                           ` Martin Dalecki
2002-03-03  7:07                 ` [PATCH] Lightweight userspace semaphores Rusty Russell
2002-03-01  4:56           ` Eric W. Biederman
2002-03-02 14:54       ` Pavel Machek
2002-02-25 15:00 ` Hubertus Franke
2002-03-01  4:44   ` Eric W. Biederman
2002-02-27  0:24 ` Rusty Russell
2002-02-27 15:53   ` Hubertus Franke
2002-03-01  0:24     ` Richard Henderson
2002-03-01  2:00       ` Hubertus Franke
2002-02-27 16:29   ` Hubertus Franke
2002-03-02 14:50   ` Hubertus Franke
2002-03-03 13:30   ` Rusty Russell
2002-03-04 16:51     ` Hubertus Franke
2002-03-05  4:41     ` Rusty Russell
2002-02-27  8:43 [PATCH] Lightweight userspace semphores Martin Wirth
2002-02-27 15:24 ` Hubertus Franke
2002-02-27 17:17   ` Martin Wirth
2002-02-27 19:04     ` Hubertus Franke
     [not found]       ` <3C7FDF76.9040903@dlr.de>
2002-03-02 14:08         ` [PATCH] Lightweight userspace semaphores Hubertus Franke
     [not found] <20020227163834.GF322@reload.nmd.msu.ru>
2002-02-27 16:58 ` Hubertus Franke
     [not found]   ` <20020227173307.GH322@reload.nmd.msu.ru>
2002-02-27 22:09     ` Hubertus Franke

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=E16f85L-0005QM-00@wagner.rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=bcrl@redhat.com \
    --cc=david@mysql.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@hairy.beasts.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.com \
    --cc=wli@holomorphy.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®