mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randazzo, Michael" <RANDAZZO@ddc-web.com>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
	"Randazzo, Michael" <RANDAZZO@ddc-web.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: Kernel 2.x POSIX Compliance/Conformance...
Date: Wed, 4 Feb 2004 15:18:17 -0500	[thread overview]
Message-ID: <89760D3F308BD41183B000508BAFAC4104B16F38@DDCNYNTD> (raw)

Where are the kernel calls defined for locks and semaphores?

How come the kernel headers don't define Posix.4 
semaphores (_POSIX_SEMAPHROES) or Posix itself
(_POSIX_VERSION is undefined)

M.

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Wednesday, February 04, 2004 2:59 PM
To: Randazzo, Michael
Cc: 'linux-kernel@vger.kernel.org'
Subject: Re: Kernel 2.x POSIX Compliance/Conformance... 


On Wed, 04 Feb 2004 14:44:00 EST, "Randazzo, Michael" said:
> I was using at sem_close(), sem_destroy90, sem_open() ...
> 
> according to Posix.4, these are defined in semaphore.h - but
> are not defined in /lib/modules/<uname -r>/build/include/semaphore.h
> 
> Are Posix.4 calls only for userspace?

System calls in general are for userspace.  Often, there exist alternate
entry points for kernel services, or other ways to do it (for instance,
the kernel has its own code for locks and semaphores).
 
"This message may contain company proprietary information. If you are not
the intended recipient, any disclosure, copying, distribution or reliance on
the contents of this message is prohibited. If you received this message in
error, please delete and notify me."


             reply	other threads:[~2004-02-04 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 20:18 Randazzo, Michael [this message]
2004-02-04 20:21 ` Valdis.Kletnieks
2004-02-04 20:51 ` Torrey Hoffman
2004-02-04 21:02 ` J.A. Magallon
  -- strict thread matches above, loose matches on Subject: below --
2004-02-04 20:22 Randazzo, Michael
2004-02-04 21:39 ` Richard B. Johnson
2004-02-04 19:44 Randazzo, Michael
2004-02-04 19:58 ` Valdis.Kletnieks
2004-02-04 19:30 Randazzo, Michael
2004-02-04 19:40 ` Valdis.Kletnieks

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=89760D3F308BD41183B000508BAFAC4104B16F38@DDCNYNTD \
    --to=randazzo@ddc-web.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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®