public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: John Stultz <john.stultz@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Robert Love <rlove@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hughd@google.com>, Mel Gorman <mel@csn.ul.ie>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Rik van Riel <riel@redhat.com>, Eric Anholt <eric@anholt.net>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [RFC][PATCH] Anonymous shared memory (ashmem) subsystem
Date: Mon, 18 Jul 2011 22:19:47 -0400	[thread overview]
Message-ID: <20110719021947.GA16986@infradead.org> (raw)
In-Reply-To: <1311015274-28650-1-git-send-email-john.stultz@linaro.org>

On Mon, Jul 18, 2011 at 11:54:34AM -0700, John Stultz wrote:
> From: Robert Love <rlove@google.com>
> 
> Recently, Robert Love updated his ashmem patch and posted it here:
> 	http://www.kernel.org/pub/linux/kernel/people/rml/ashmem/
> 
> This reminded me that in all the conversations around the Android patches,
> I've not seen any discussion on lkml about the ashmem functionality. 
> Coming from Robert, its very clean and self-contained and seems pretty
> interesting. So I wanted to send it out for review and comments.

And utterly stupid, just use tmpfs and /dev/zero for the base functionality.

And the pinning crap really needs a much better rationale.


  reply	other threads:[~2011-07-19  2:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 18:54 [RFC][PATCH] Anonymous shared memory (ashmem) subsystem John Stultz
2011-07-19  2:19 ` Christoph Hellwig [this message]
2011-07-19  3:32   ` Bryan Donlan
2011-07-19  3:36     ` Christoph Hellwig
2011-07-19 15:37       ` Dave Hansen
2011-07-19 15:41         ` Christoph Hellwig
2011-07-19 21:58           ` John Stultz
2011-07-19 14:33 ` Christoph Lameter
2011-07-19 15:55 ` Arnd Bergmann

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=20110719021947.GA16986@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=eric@anholt.net \
    --cc=hughd@google.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=riel@redhat.com \
    --cc=rlove@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