From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752602AbaAXNWh (ORCPT ); Fri, 24 Jan 2014 08:22:37 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:57357 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752112AbaAXNWg (ORCPT ); Fri, 24 Jan 2014 08:22:36 -0500 Date: Fri, 24 Jan 2014 05:22:34 -0800 From: Christoph Hellwig To: Jens Axboe Cc: linux-kernel@vger.kernel.org Subject: ipi_redirect vs rq_affinity Message-ID: <20140124132234.GA8553@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Hi Jens, it seems like blk-mq uses the ipi_redirect attribute in pretty much the same way as the old blk-softirq code used the rq_affinity one, except that the old code has an additional option to direct into any core in the current package. Is there any good reason to not reuse the old name and semantics?