Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031772AbbDXQGu (ORCPT ); Fri, 24 Apr 2015 12:06:50 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41628 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030417AbbDXQGr (ORCPT ); Fri, 24 Apr 2015 12:06:47 -0400 Message-ID: <553A6A0F.2010808@redhat.com> Date: Fri, 24 Apr 2015 12:06:39 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Christoph Lameter , "Paul E. McKenney" CC: Benjamin Herrenschmidt , Jerome Glisse , linux-kernel@vger.kernel.org, linux-mm@kvack.org, jglisse@redhat.com, mgorman@suse.de, aarcange@redhat.com, airlied@redhat.com, aneesh.kumar@linux.vnet.ibm.com, Cameron Buschardt , Mark Hairgrove , Geoffrey Gerfin , John McKenna , akpm@linux-foundation.org Subject: Re: Interacting with coherent memory on external devices References: <1429663372.27410.75.camel@kernel.crashing.org> <20150422005757.GP5561@linux.vnet.ibm.com> <1429664686.27410.84.camel@kernel.crashing.org> <20150422163135.GA4062@gmail.com> <1429756456.4915.22.camel@kernel.crashing.org> <20150423185240.GO5561@linux.vnet.ibm.com> <20150424145459.GY5561@linux.vnet.ibm.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1272 Lines: 33 On 04/24/2015 11:49 AM, Christoph Lameter wrote: > On Fri, 24 Apr 2015, Paul E. McKenney wrote: > >> can deliver, but where the cost of full-fledge hand tuning cannot be >> justified. >> >> You seem to believe that this latter category is the empty set, which >> I must confess does greatly surprise me. > > If there are already compromises are being made then why would you want to > modify the kernel for this? Some user space coding and device drivers > should be sufficient. You assume only one program at a time would get to use the GPU for accelerated computations, and the GPU would get dedicated to that program. That will not be the case when you have libraries using the GPU for computations. There could be dozens of programs in the system using that library, with no knowledge of how many GPU resources are used by the other programs. There is a very clear cut case for having the OS manage the GPU resources transparently, just like it does for all the other resources in the system. -- All rights reversed -- 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/