linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <andi@firstfloor.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Ingo Molnar <mingo@redhat.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Hugh Dickins <hugh@veritas.com>,
	Ulrich Drepper <drepper@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH, v3] shmat: introduce flag SHM_MAP_NOT_FIXED
Date: Wed, 8 Oct 2008 00:40:30 +0100	[thread overview]
Message-ID: <20081008004030.7a0e9915@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20081007232059.GU20740@one.firstfloor.org>

> > 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? 

Actually you can do so. As it stands today the SYS3 SHM interface code
does the following

	create a char array in the form SYS%08ld, key
	open it on shmfs

> - 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) 

They can be changed and nobody is wanting to map those at fixed addresses.

> - An system call emulation as in qemu obviously has to implement the
> existing system call semantics.

Which it can do perfectly well using shm_open to create its SYS3
SHM objects. In fact theoertically we could bin the whole of SYS3 shm and
push it into glibc emulation if we wanted.

Alan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-10-07 23:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 16:15 Kirill A. Shutemov
2008-10-07 16:31 ` KOSAKI Motohiro
2008-10-07 21:10   ` Andi Kleen
2008-10-07 21:38     ` KOSAKI Motohiro
2008-10-07 23:23       ` Andi Kleen
2008-10-07 23:05     ` Alan Cox
2008-10-07 23:20       ` Andi Kleen
2008-10-07 23:40         ` Alan Cox [this message]
2008-10-07 23:57           ` Andi Kleen
2008-10-08  8:33             ` Alan Cox
2008-10-08  8:34             ` Alan Cox
2008-10-08  8:43               ` Andi Kleen
2008-10-08  8:58                 ` Alan Cox
2008-10-08  9:11                   ` Andi Kleen
2008-10-08 10:20                     ` Alan Cox
2008-10-08 11:02                       ` Andi Kleen
2008-10-08 12:46                         ` Alan Cox
2008-10-07 16:54 ` Alan Cox
2008-10-08  8:57 ` Michael Kerrisk
2008-10-08  9:35   ` Kirill A. Shutemov

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=20081008004030.7a0e9915@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=drepper@redhat.com \
    --cc=hugh@veritas.com \
    --cc=kirill@shutemov.name \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    /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