Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261541AbVAGT11 (ORCPT ); Fri, 7 Jan 2005 14:27:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261535AbVAGT0D (ORCPT ); Fri, 7 Jan 2005 14:26:03 -0500 Received: from peabody.ximian.com ([130.57.169.10]:27042 "EHLO peabody.ximian.com") by vger.kernel.org with ESMTP id S261547AbVAGTZm (ORCPT ); Fri, 7 Jan 2005 14:25:42 -0500 Subject: Re: [RFC] per thread page reservation patch From: Robert Love To: Christoph Hellwig Cc: Vladimir Saveliev , linux-mm , Andrew Morton , "linux-kernel@vger.kernel.org" In-Reply-To: <20050107190545.GA13898@infradead.org> References: <20050103011113.6f6c8f44.akpm@osdl.org> <20050103114854.GA18408@infradead.org> <41DC2386.9010701@namesys.com> <1105019521.7074.79.camel@tribesman.namesys.com> <20050107144644.GA9606@infradead.org> <1105118217.3616.171.camel@tribesman.namesys.com> <20050107190545.GA13898@infradead.org> Content-Type: text/plain Date: Fri, 07 Jan 2005 14:21:16 -0500 Message-Id: <1105125676.9311.27.camel@betsy.boston.ximian.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 670 Lines: 25 On Fri, 2005-01-07 at 19:05 +0000, Christoph Hellwig wrote: > int perthread_pages_reserve(int nrpages, int gfp) > { > LIST_HEAD(accumulator); > int i; > > list_splice_init(¤t->private_pages, &accumulator); > > Now the big question is, what's synchronizing access to > current->private_pages? Safe without locks so long as there is no other way to get at another process's private_pages. ;) Best, Robert Love - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/