From: Kay Sievers <kay@vrfy.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: John Stultz <john.stultz@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Greg KH <gregkh@linuxfoundation.org>,
Android Kernel Team <kernel-team@android.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>,
Michel Lespinasse <walken@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Neil Brown <neilb@suse.de>,
Andrea Arcangeli <aarcange@redhat.com>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Minchan Kim <minchan@kernel.org>,
Lennart Poettering <mzxreary@0pointer.de>
Subject: Re: [RFC] shmgetfd idea
Date: Thu, 30 Jan 2014 17:02:40 +0100 [thread overview]
Message-ID: <CAPXgP13rAYV9SEQ0jgzD2C2vwWVxgqQfD__+ooAQcoPUu-RXhQ@mail.gmail.com> (raw)
In-Reply-To: <20140130084657.GA31508@infradead.org>
On Thu, Jan 30, 2014 at 9:46 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Mon, Jan 27, 2014 at 05:37:04PM -0800, John Stultz wrote:
>> In working with ashmem and looking briefly at kdbus' memfd ideas,
>> there's a commonality that both basically act as a method to provide
>> applications with unlinked tmpfs/shmem fds.
>
> Just use O_TMPFILE on a tmpfs file and you're done.
Ashmem and kdbus can name the deleted files, which is useful for
debugging and tools to show the associated name for the file
descriptor. They also show up in /proc/$PID/maps/ and possibly in
/proc/$PID/fd/.
O_TMPFILE always creates files with just the name "/". Unless that is
changed we wouldn't want switch over to O_TMPFILE, because we would
lose that nice feature.
Is there are way to "fix" O_TMPFILE to accept the name of the file to
be created, instead of insisting to take only the leading directory as
the argument?
Kay
--
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:[~2014-01-30 16:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:37 John Stultz
2014-01-28 1:53 ` Kay Sievers
2014-01-28 19:47 ` John Stultz
2014-01-28 3:52 ` H. Peter Anvin
2014-01-28 19:56 ` John Stultz
2014-01-28 20:37 ` H. Peter Anvin
2014-01-28 20:58 ` John Stultz
2014-01-28 21:01 ` Kay Sievers
2014-01-28 21:05 ` John Stultz
2014-01-28 21:10 ` H. Peter Anvin
2014-01-28 21:54 ` John Stultz
2014-01-28 22:14 ` Kay Sievers
2014-01-28 23:02 ` H. Peter Anvin
2014-01-28 23:14 ` Kay Sievers
2014-01-28 23:19 ` H. Peter Anvin
2014-01-29 0:14 ` Kay Sievers
2014-01-29 0:20 ` H. Peter Anvin
2014-01-29 0:49 ` Kay Sievers
2014-01-28 23:14 ` John Stultz
2014-01-28 21:28 ` Kay Sievers
2014-01-30 8:46 ` Christoph Hellwig
2014-01-30 16:02 ` Kay Sievers [this message]
2014-01-30 21:42 ` John Stultz
2014-01-31 0:01 ` Kay Sievers
2014-02-03 15:03 ` Christoph Hellwig
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=CAPXgP13rAYV9SEQ0jgzD2C2vwWVxgqQfD__+ooAQcoPUu-RXhQ@mail.gmail.com \
--to=kay@vrfy.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=hpa@linux.intel.com \
--cc=hughd@google.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mzxreary@0pointer.de \
--cc=neilb@suse.de \
--cc=riel@redhat.com \
--cc=takahiro.akashi@linaro.org \
--cc=walken@google.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