From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lauri Kasanen Subject: Re: [RFC 0/3] TTM priority queue logic Date: Mon, 7 Apr 2014 17:39:08 +0300 Message-ID: <20140407173908.8d623569.cand@gmx.com> References: <20140404165224.a4856af5.cand@gmx.com> <53429938.3050203@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by gabe.freedesktop.org (Postfix) with ESMTP id D89786E69F for ; Mon, 7 Apr 2014 07:38:40 -0700 (PDT) In-Reply-To: <53429938.3050203@vmware.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Thomas Hellstrom Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Mon, 07 Apr 2014 14:25:28 +0200 Thomas Hellstrom wrote: > Hi, Lauri. > > On 04/04/2014 03:52 PM, Lauri Kasanen wrote: > > Hi list, Thomas, > > > > I'd like to know if this is going in the right direction. > > This looks fine with me. > > However, if possible I'd like the drivers to enable both alloc_threshold > and priority queue on a per-memory-type basis. > > That would mean no new arguments (use_pqueue, alloc_threshold) in > ttm_bo_device_init(). Instead, set default values in > ttm_bo_init_mm(), and let the driver change them in the init_mem_type() > callback. > > Do you think that would work? Thanks for the review. Alloc_threshold was removed, and the current patch (in drm-next) replaced it with a placement flag. So now that logic is in the driver. Making the pqueue a per-type option would certainly work, I'll edit it to do so. I don't see why it would improve GTT or SYSTEM given their perf characteristics, but I suppose future devices can always do weird things. - Lauri