From: Sam Ben <sam.bennn@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alex Elsayed <eternaleye@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: RFC: named anonymous vmas
Date: Sun, 14 Jul 2013 08:57:13 +0800 [thread overview]
Message-ID: <51E1F769.7090208@gmail.com> (raw)
In-Reply-To: <20130624114832.GA9961@infradead.org>
Hi Christoph,
On 06/24/2013 07:48 PM, Christoph Hellwig wrote:
> On Sat, Jun 22, 2013 at 12:47:29PM -0700, Alex Elsayed wrote:
>> Couldn't this be done by having a root-only tmpfs, and having a userspace
>> component that creates per-app directories with restrictive permissions on
>> startup/app install? Then each app creates files in its own directory, and
>> can pass the fds around.
> Honestly having a device that allows passing fds around that can be
> mmaped sounds a lot simpler. I have to admit that I expect /dev/zero
> to do this, but looking at the code it creates new file structures
> at ->mmap time which would defeat this.
Could you point out where done this?
>
> --
> 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>
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ben <sam.bennn@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alex Elsayed <eternaleye@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: RFC: named anonymous vmas
Date: Sun, 14 Jul 2013 08:57:13 +0800 [thread overview]
Message-ID: <51E1F769.7090208@gmail.com> (raw)
In-Reply-To: <20130624114832.GA9961@infradead.org>
Hi Christoph,
On 06/24/2013 07:48 PM, Christoph Hellwig wrote:
> On Sat, Jun 22, 2013 at 12:47:29PM -0700, Alex Elsayed wrote:
>> Couldn't this be done by having a root-only tmpfs, and having a userspace
>> component that creates per-app directories with restrictive permissions on
>> startup/app install? Then each app creates files in its own directory, and
>> can pass the fds around.
> Honestly having a device that allows passing fds around that can be
> mmaped sounds a lot simpler. I have to admit that I expect /dev/zero
> to do this, but looking at the code it creates new file structures
> at ->mmap time which would defeat this.
Could you point out where done this?
>
> --
> 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>
next prev parent reply other threads:[~2013-07-14 0:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 23:42 RFC: named anonymous vmas Colin Cross
2013-06-21 23:42 ` Colin Cross
2013-06-22 5:12 ` Kyungmin Park
2013-06-22 5:12 ` Kyungmin Park
2013-06-22 5:20 ` Colin Cross
2013-06-22 5:20 ` Colin Cross
2013-06-22 10:31 ` Christoph Hellwig
2013-06-22 10:31 ` Christoph Hellwig
2013-06-22 17:30 ` Colin Cross
2013-06-22 17:30 ` Colin Cross
2013-06-22 19:47 ` Alex Elsayed
2013-06-24 11:48 ` Christoph Hellwig
2013-06-24 11:48 ` Christoph Hellwig
2013-06-24 17:26 ` Colin Cross
2013-06-24 17:26 ` Colin Cross
2013-06-24 23:45 ` John Stultz
2013-06-24 23:45 ` John Stultz
2013-06-26 18:53 ` Alex Elsayed
2013-07-14 0:57 ` Sam Ben [this message]
2013-07-14 0:57 ` Sam Ben
2013-08-01 8:29 ` Christoph Hellwig
2013-08-01 8:29 ` Christoph Hellwig
2013-08-01 8:36 ` Rich Felker
2013-08-01 8:36 ` Rich Felker
2013-08-02 15:11 ` Christoph Hellwig
2013-08-02 15:11 ` Christoph Hellwig
2013-08-03 23:54 ` KOSAKI Motohiro
2013-08-03 23:54 ` KOSAKI Motohiro
2013-07-14 0:27 ` Sam Ben
2013-07-14 0:27 ` Sam Ben
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=51E1F769.7090208@gmail.com \
--to=sam.bennn@gmail.com \
--cc=eternaleye@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.