From: Mel Gorman <mgorman@suse.de>
To: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, cyeoh@au1.ibm.com
Subject: Re: Suggestion, "public process scoped interfaces"
Date: Wed, 2 Apr 2014 23:15:08 +0100 [thread overview]
Message-ID: <20140402221508.GB1869@suse.de> (raw)
In-Reply-To: <fa9ecac225ee2.533c5ee6@langara.bc.ca>
On Wed, Apr 02, 2014 at 07:03:02PM +0000, Steven Stewart-Gallus wrote:
> Hello,
>
> I have been reconsidering requirements and solutions brought up in my
> post "How about allowing processes to expose memory for cross memory
> attaching?".
commit fcf634098c00dd9cd247447368495f0b79be12d1
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2014-04-02 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 19:03 Suggestion, "public process scoped interfaces" Steven Stewart-Gallus
2014-04-02 22:15 ` Mel Gorman [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=20140402221508.GB1869@suse.de \
--to=mgorman@suse.de \
--cc=cyeoh@au1.ibm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sstewartgallus00@mylangara.bc.ca \
/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