From: Jakub Jelinek <jakub@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Steven_Snyder@3com.com, linux-kernel@vger.kernel.org
Subject: Re: State of Posix compliance in v2.2/v2.4 kernel?
Date: Mon, 13 Nov 2000 11:13:19 -0500 [thread overview]
Message-ID: <20001113111319.E1514@devserv.devel.redhat.com> (raw)
In-Reply-To: <88256996.00577D9E.00@hqoutbound.ops.3com.com> <3A101009.5F05DA18@mandrakesoft.com>
In-Reply-To: <3A101009.5F05DA18@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, Nov 13, 2000 at 11:00:09AM -0500
On Mon, Nov 13, 2000 at 11:00:09AM -0500, Jeff Garzik wrote:
> Steven_Snyder@3com.com wrote:
> > Sorry if this is a FAQ, but I've searched the archives for this list
> > (http://www.uwsg.iu.edu/hypermail/linux/kernel/) and only come with references
> > from 1996!
> >
> > What is the state of Posix-compliant services (threads, semaphores, timers,
> > etc.) in the current (v2.2/v2.4) Linux kernels?
>
> IMHO this is a question better asked of glibc people, not kernel people.
>
> The kernel does its best to facilitate POSIX compliances,
Well, it does not do its best. There are several areas where kernel should
help, things like POSIX semaphores would be much faster with kernel support,
likewise threads if some things Ulrich stated here a couple of months
ago were done in the kernel, POSIX message queue passing is not doable in
userland without kernel help either (I have a message queue filesystem
kernel patch for this, but it is a 2.5 thing).
Jakub
-
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 prev parent reply other threads:[~2000-11-13 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 15:54 State of Posix compliance in v2.2/v2.4 kernel? Steven_Snyder
2000-11-13 16:00 ` Jeff Garzik
2000-11-13 16:13 ` Jakub Jelinek [this message]
2000-11-13 16:17 ` Jeff Garzik
2000-11-13 18:31 ` Gary Lawrence Murphy
2000-11-19 10:24 ` GOTO Masanori
2000-11-19 13:30 ` POSIX message queue passing (was Re: State of Posix compliance in v2.2/v2.4 kernel?) Jakub Jelinek
2000-11-13 16:40 ` State of Posix compliance in v2.2/v2.4 kernel? Guest section DW
2000-11-13 20:28 ` Ingo Oeser
-- strict thread matches above, loose matches on Subject: below --
2000-11-13 16:09 Dunlap, Randy
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=20001113111319.E1514@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Steven_Snyder@3com.com \
--cc=jgarzik@mandrakesoft.com \
--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