Re: Multithreaded locks.c

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Sat Nov 04 2000 - 13:20:19 EST

Next message: Russell King: "Re: USB init order dependencies."
Previous message: Alan Cox: "Re: processes> 2^15"
In reply to: Andrew Morton: "Multithreaded locks.c"
Next in thread: Andrew Morton: "Re: Multithreaded locks.c"
Reply: Andrew Morton: "Re: Multithreaded locks.c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> have got it right. Does anyone know what this part of the
> flock(2) manpage means?
>
> A single file may not simultaneously have both shared and
> exclusive locks.

AFAIK its saying LOCK_EX is exclusive and blocks shared locks and vice
versa. Its a standard reader-writer lock setup. LOCK_EX is writer, LOCK_SH
is reader.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Russell King: "Re: USB init order dependencies."
Previous message: Alan Cox: "Re: processes> 2^15"
In reply to: Andrew Morton: "Multithreaded locks.c"
Next in thread: Andrew Morton: "Re: Multithreaded locks.c"
Reply: Andrew Morton: "Re: Multithreaded locks.c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:16 EST