From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerome Glisse Subject: Re: [PATCH v2 00/25] AMDKFD kernel driver Date: Mon, 21 Jul 2014 19:36:14 -0400 Message-ID: <20140721233613.GB6422@gmail.com> References: <20140721155437.GA4519@gmail.com> <53CD5122.5040804@amd.com> <20140721181433.GA5196@gmail.com> <53CD5DBC.7010301@amd.com> <20140721185940.GA5278@gmail.com> <53CD68BF.4020308@amd.com> <20140721192837.GC5278@gmail.com> <53CD8C7D.9010106@amd.com> <20140721230535.GA6422@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com [209.85.216.176]) by gabe.freedesktop.org (Postfix) with ESMTP id 6AFE06E07F for ; Mon, 21 Jul 2014 16:36:15 -0700 (PDT) Received: by mail-qc0-f176.google.com with SMTP id i17so5669463qcy.7 for ; Mon, 21 Jul 2014 16:36:14 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: "Bridgman, John" Cc: "Lewycky, Andrew" , linux-mm , "Daenzer, Michel" , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , "Pinchuk, Evgeny" , "Skidanov, Alexey" , Andrew Morton List-Id: dri-devel@lists.freedesktop.org On Mon, Jul 21, 2014 at 11:29:23PM +0000, Bridgman, John wrote: > >> >> So even if I really wanted to, and I may agree with you > >> >> theoretically on that, I can't fulfill your desire to make the > >> >> "kernel being able to preempt at any time and be able to decrease > >> >> or increase user queue priority so overall kernel is in charge of > >> >> resources management and it can handle rogue client in proper > >> >> fashion". Not in KV, and I guess not in CZ as well. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > >Also it is a worrisome prospect of seeing resource management completely > >ignore for future AMD hardware. Kernel exist for a reason ! Kernel main > >purpose is to provide resource management if AMD fails to understand tha= t, > >this is not looking good on long term and i expect none of the HSA > >technology will get momentum and i would certainly advocate against any > >use of it inside product i work on. > = > Hi Jerome; > = > I was following along until the above comment. It seems to be the exact o= pposite of what Oded has been saying, which is that future AMD hardware *do= es* have more capabilities for resource management and that we do have some= capabilities today. Can you help me understand what the comment it was bas= ed on ? Highlighted above. Cheers, J=E9r=F4me From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f42.google.com (mail-qg0-f42.google.com [209.85.192.42]) by kanga.kvack.org (Postfix) with ESMTP id 9035F6B0038 for ; Mon, 21 Jul 2014 19:36:15 -0400 (EDT) Received: by mail-qg0-f42.google.com with SMTP id j5so6374967qga.29 for ; Mon, 21 Jul 2014 16:36:15 -0700 (PDT) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [2607:f8b0:400d:c00::230]) by mx.google.com with ESMTPS id h10si18849014qgd.93.2014.07.21.16.36.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jul 2014 16:36:14 -0700 (PDT) Received: by mail-qa0-f48.google.com with SMTP id m5so5787449qaj.7 for ; Mon, 21 Jul 2014 16:36:14 -0700 (PDT) Date: Mon, 21 Jul 2014 19:36:14 -0400 From: Jerome Glisse Subject: Re: [PATCH v2 00/25] AMDKFD kernel driver Message-ID: <20140721233613.GB6422@gmail.com> References: <20140721155437.GA4519@gmail.com> <53CD5122.5040804@amd.com> <20140721181433.GA5196@gmail.com> <53CD5DBC.7010301@amd.com> <20140721185940.GA5278@gmail.com> <53CD68BF.4020308@amd.com> <20140721192837.GC5278@gmail.com> <53CD8C7D.9010106@amd.com> <20140721230535.GA6422@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: "Bridgman, John" Cc: "Gabbay, Oded" , "Lewycky, Andrew" , "Pinchuk, Evgeny" , "Daenzer, Michel" , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , linux-mm , "Skidanov, Alexey" , Andrew Morton On Mon, Jul 21, 2014 at 11:29:23PM +0000, Bridgman, John wrote: > >> >> So even if I really wanted to, and I may agree with you > >> >> theoretically on that, I can't fulfill your desire to make the > >> >> "kernel being able to preempt at any time and be able to decrease > >> >> or increase user queue priority so overall kernel is in charge of > >> >> resources management and it can handle rogue client in proper > >> >> fashion". Not in KV, and I guess not in CZ as well. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > >Also it is a worrisome prospect of seeing resource management completely > >ignore for future AMD hardware. Kernel exist for a reason ! Kernel main > >purpose is to provide resource management if AMD fails to understand that, > >this is not looking good on long term and i expect none of the HSA > >technology will get momentum and i would certainly advocate against any > >use of it inside product i work on. > > Hi Jerome; > > I was following along until the above comment. It seems to be the exact opposite of what Oded has been saying, which is that future AMD hardware *does* have more capabilities for resource management and that we do have some capabilities today. Can you help me understand what the comment it was based on ? Highlighted above. Cheers, Jerome -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751341AbaGUXgR (ORCPT ); Mon, 21 Jul 2014 19:36:17 -0400 Received: from mail-qc0-f170.google.com ([209.85.216.170]:37048 "EHLO mail-qc0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751048AbaGUXgP (ORCPT ); Mon, 21 Jul 2014 19:36:15 -0400 Date: Mon, 21 Jul 2014 19:36:14 -0400 From: Jerome Glisse To: "Bridgman, John" Cc: "Gabbay, Oded" , "Lewycky, Andrew" , "Pinchuk, Evgeny" , "Daenzer, Michel" , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , linux-mm , "Skidanov, Alexey" , Andrew Morton Subject: Re: [PATCH v2 00/25] AMDKFD kernel driver Message-ID: <20140721233613.GB6422@gmail.com> References: <20140721155437.GA4519@gmail.com> <53CD5122.5040804@amd.com> <20140721181433.GA5196@gmail.com> <53CD5DBC.7010301@amd.com> <20140721185940.GA5278@gmail.com> <53CD68BF.4020308@amd.com> <20140721192837.GC5278@gmail.com> <53CD8C7D.9010106@amd.com> <20140721230535.GA6422@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 21, 2014 at 11:29:23PM +0000, Bridgman, John wrote: > >> >> So even if I really wanted to, and I may agree with you > >> >> theoretically on that, I can't fulfill your desire to make the > >> >> "kernel being able to preempt at any time and be able to decrease > >> >> or increase user queue priority so overall kernel is in charge of > >> >> resources management and it can handle rogue client in proper > >> >> fashion". Not in KV, and I guess not in CZ as well. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > >Also it is a worrisome prospect of seeing resource management completely > >ignore for future AMD hardware. Kernel exist for a reason ! Kernel main > >purpose is to provide resource management if AMD fails to understand that, > >this is not looking good on long term and i expect none of the HSA > >technology will get momentum and i would certainly advocate against any > >use of it inside product i work on. > > Hi Jerome; > > I was following along until the above comment. It seems to be the exact opposite of what Oded has been saying, which is that future AMD hardware *does* have more capabilities for resource management and that we do have some capabilities today. Can you help me understand what the comment it was based on ? Highlighted above. Cheers, Jérôme