From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757271Ab2DXTVu (ORCPT ); Tue, 24 Apr 2012 15:21:50 -0400 Received: from merlin.infradead.org ([205.233.59.134]:40997 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756998Ab2DXTVt convert rfc822-to-8bit (ORCPT ); Tue, 24 Apr 2012 15:21:49 -0400 Message-ID: <1335295291.28150.222.camel@twins> Subject: Re: [PATCH 3/3] [RFC] ashmem: Convert ashmem to use volatile ranges From: Peter Zijlstra To: John Stultz Cc: LKML , Andrew Morton , Android Kernel Team , Robert Love , Mel Gorman , Hugh Dickins , Dave Hansen , Rik van Riel , Dmitry Adamushko , Dave Chinner , Neil Brown , Andrea Righi , "Aneesh Kumar K.V" Date: Tue, 24 Apr 2012 21:21:31 +0200 In-Reply-To: <1335289787-11089-4-git-send-email-john.stultz@linaro.org> References: <1335289787-11089-1-git-send-email-john.stultz@linaro.org> <1335289787-11089-4-git-send-email-john.stultz@linaro.org> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2012-04-24 at 10:49 -0700, John Stultz wrote: > First pass attempt at getting ashmem to utilize the volatile range > code. One would think the purpose of the previous patches was to entirely do away with the ashmem interface.. this patch is a temporary band-aid to assist in testing without having to modify userspace?