From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751151AbaEBFFc (ORCPT ); Fri, 2 May 2014 01:05:32 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:39606 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750819AbaEBFFb (ORCPT ); Fri, 2 May 2014 01:05:31 -0400 Date: Thu, 1 May 2014 22:05:23 -0700 From: Christoph Hellwig To: Jens Axboe Cc: Kent Overstreet , Ming Lei , Alexander Gordeev , Linux Kernel Mailing List , Shaohua Li , Nicholas Bellinger , Ingo Molnar , Peter Zijlstra Subject: Re: [PATCH RFC 0/2] percpu_ida: Take into account CPU topology when stealing tags Message-ID: <20140502050523.GA21708@infradead.org> References: <535716A5.6050108@kernel.dk> <535AD235.90604@kernel.dk> <535B13D7.4050202@kernel.dk> <53601602.5060306@kernel.dk> <20140501224744.GA2285@kmo-pixel> <536300BB.5060906@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <536300BB.5060906@kernel.dk> User-Agent: Mutt/1.5.21 (2010-09-15) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 01, 2014 at 08:19:39PM -0600, Jens Axboe wrote: > I've taken the consequence of this and implemented another tagging > scheme that blk-mq will use if it deems that percpu_ida isn't going > to be effective for the device being initialized. But I really hate > to have both of them in there. Unfortunately I have no devices > available that have a tag space that will justify using percu_ida, > so comparisons are a bit hard at the moment. NVMe should change > that, though, so decision will have to be deferred until that is > tested. At least for SCSI devices _tag space_ is plenty, it's just the we artifically limit our tag space to the queue depth to avoid having to track that one separately. In addition we also preallocaste a request for each tag, so even if we would track the queue depth separately we would waste a lot of memory.