Re: linux:sys_ipc syscall

[Michal Simek <monstr at monstr dot eu>]

David Bartley wrote:
> On Wed, May 6, 2009 at 11:06 AM, Mike Frysinger <vapier@gentoo.org> wrote:
>> On Monday 04 May 2009 10:05:51 Michal Simek wrote:
>>> I would like to ask you if someone from you work on separate ipc syscalls.
>>> I mean that all code call one sys_ipc syscall not separate syscall like
>>> sys_semctl, sys_semget, sys_semop, sys_msgctl,
>>> sys_msgget, sys_msgrcv, sys_msgsnd, sys_shmat, sys_shmctl, sys_shmdt,
>>> sys_shmget.
>> sorry, but what's the question exactly ?
> 
> I think he wants to know why glibc on Linux uses SYS_ipc to implement
> msgctl, etc... rather than SYS_msgctl, etc...

I don't want to know why is used sys_ipc rather than sys_msgctl.
I think there were some historical reasons for that.

But I wanted to know if someone have patches on it because I would like to
remove sys_ipc from Microblaze syscall table and of course sys_ipc implementation.
For that I need to have support for separate ipc syscalls in glibc.

Michal

> 
> -- David


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854