Messages in this thread | | | Date | Sat, 17 Apr 2004 12:49:08 +0200 | From | Manfred Spraul <> | Subject | Re: POSIX message queues, libmqueue: mq_open, mq_unlink |
| |
Alex wrote:
>Ok. It's just that every provider of the _kernel_ interface to user >space has now to take care of being posix-compliant. Write the code for >checks, iow. That is not the case for "open", for instance. >And besides, with the patch applied the kernel is also posix compliant, >isn't it? > No. E.g. mq_notify(,&{.sigev_notify=SIGEV_THREAD) cannot be implemented in kernel space. And sys_mq_getsetattr isn't posix compliant either - the user space library must implement mq_getattr and mq_setattr on top of the kernel API. The kernel API was designed to be simple and flexible. Perhaps we want to extend the kernel implementation in the future, and then a leading slash could be used to indicate that we are using the new features.
-- Manfred
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |