lkml.org 
[lkml]   [2008]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH, v3] shmat: introduce flag SHM_MAP_NOT_FIXED
On Wed, Oct 08, 2008 at 12:05:18AM +0100, Alan Cox wrote:
> On Tue, 7 Oct 2008 23:10:38 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
>
> > > Sorry, no.
> > > This description still doesn't explain why this interface is needed.
> > >
> > > The one of the points is this interface is used by another person or not.
> > > You should explain how large this interface benefit has.
> > >
> > > Andi kleen explained this interface _can_ be used another one.
> > > but nobody explain who use it actually.
> >
> > Anyone who doesn't want to use fixed addresses.
>
> Can use shm_open and mmap to get POSIX standard shm behaviour via a sane

I don't think shm_open can attach to SYSV shared segments. Or are you
proposing to add "sysvshmfs" to make that possible?

> interface without adding more crap to the sys3 shm madness.
>
> Sorry this patch is completely bogus - introduce the user programs
> involved to 1990s technology.

As already listed in an earlier email, but here again:

- There are legacy interfaces that cannot be really changed who use sysv shm
(e.g. X shm and others -- just do a ipcs on your system)
- An system call emulation as in qemu obviously has to implement the
existing system call semantics.

-Andi

--
ak@linux.intel.com


\
 
 \ /
  Last update: 2008-10-08 01:17    [W:0.062 / U:2.652 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site