From: Christoph Hellwig <hch@infradead.org>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Michael Hohnbaum <hohnbaum@us.ibm.com>,
lse-tech@lists.sourceforge.net, Andrew Morton <akpm@digeo.com>,
linux-mm@kvack.org
Subject: Re: [rfc][api] Shared Memory Binding
Date: Tue, 11 Feb 2003 21:20:26 +0000 [thread overview]
Message-ID: <20030211212026.A21174@infradead.org> (raw)
In-Reply-To: <3E49635A.70906@us.ibm.com>; from colpatch@us.ibm.com on Tue, Feb 11, 2003 at 12:55:54PM -0800
On Tue, Feb 11, 2003 at 12:55:54PM -0800, Matthew Dobson wrote:
> Hello All,
> I've got a pseudo manpage for a new call I'm attempting to implement:
> shmbind(). The idea of the call is to allow userspace processes to bind
> shared memory segments to particular nodes' memory and do so according
> to certain policies. Processes would call shmget() as usual, but before
> calling shmat(), the process could call shmbind() to set up a binding
> for the segment. Then, any time pages from the shared segment are
> faulted into memory, it would be done according to this binding.
> Any comments about the attatched manpage, the idea in general, how to
> improve it, etc. are definitely welcome.
Do we really need to add more mess to the broken sysvipc interfaces?
I think an shm_open_on_node call for posix-style shm would be a much better
idea.
--
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/
prev parent reply other threads:[~2003-02-11 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 20:55 Matthew Dobson
2003-02-11 21:20 ` Christoph Hellwig [this message]
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=20030211212026.A21174@infradead.org \
--to=hch@infradead.org \
--cc=akpm@digeo.com \
--cc=colpatch@us.ibm.com \
--cc=hohnbaum@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.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