From: Matthew Dobson <colpatch@us.ibm.com>
To: "Luck, Tony" <tony.luck@intel.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: [Lse-tech] [rfc][api] Shared Memory Binding
Date: Tue, 11 Feb 2003 14:27:02 -0800 [thread overview]
Message-ID: <3E4978B6.9030201@us.ibm.com> (raw)
In-Reply-To: <DD755978BA8283409FB0087C39132BD1A07CD2@fmsmsx404.fm.intel.com>
Luck, Tony wrote:
>> 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.
>
>
> Why tie this to the sysV ipc shm mechanism? Couldn't you make
> a more general "mmbind()" call that applies to a "start, len"
> range of virtual addresses? This would work for your current
> usage (but you would apply it after the "shmat()"), but it would
> also be useful for memory allocated to a process with mmap(), sbrk()
> and even general .text/.data if you managed to call it before you
> touched pages.
>
> -Tony
I'd hoped to see how this proposal and pending patch went over with
everyone, before attempting anything more broad. My last attempt at
something similar to this failed due to being too invasive and
complicated. My thoughts were to try something fairly straightforward
and simple this time. The patch I'm working on to implement this could
however lead to something like what you described if desired. I'm
trying to allow for the possibility of expanding the power of bindings
with my code. And I also think that these types of bindings could be
useful in a more general way.
Cheers!
-Matt
--
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/
next prev parent reply other threads:[~2003-02-11 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 21:42 Luck, Tony
2003-02-11 21:51 ` Paul Jackson
2003-02-16 9:50 ` Christoph Hellwig
2003-02-11 22:27 ` Matthew Dobson [this message]
2003-02-13 9:48 ` Christoph Rohland
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=3E4978B6.9030201@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=akpm@digeo.com \
--cc=hohnbaum@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=tony.luck@intel.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