From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752203AbeC1GP4 (ORCPT ); Wed, 28 Mar 2018 02:15:56 -0400 Received: from mga01.intel.com ([192.55.52.88]:58265 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751750AbeC1GPz (ORCPT ); Wed, 28 Mar 2018 02:15:55 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,369,1517904000"; d="scan'208";a="41887304" Message-ID: <1522217751.9730.80.camel@gmail.com> Subject: Re: [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Thorsten Leemhuis , Ming Lei , Jens Axboe , Christoph Hellwig , Thomas Gleixner , linux-kernel@vger.kernel.org Cc: linux-block@vger.kernel.org, Laurence Oberman Date: Wed, 28 Mar 2018 09:15:51 +0300 In-Reply-To: References: <20180308105358.1506-1-ming.lei@redhat.com> <1520515113.20980.31.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 (3.26.6-1.fc27) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2018-03-26 at 10:39 +0200, Thorsten Leemhuis wrote: > Lo! Your friendly Linux regression tracker here ;-) > > On 08.03.2018 14:18, Artem Bityutskiy wrote: > > On Thu, 2018-03-08 at 18:53 +0800, Ming Lei wrote: > > > This patchset tries to spread among online CPUs as far as possible, so > > > that we can avoid to allocate too less irq vectors with online CPUs > > > mapped. > > > > […] > > Tested-by: Artem Bityutskiy > > Link: https://lkml.kernel.org/r/1519311270.2535.53.camel@intel.com > > > > this patchset fixes the v4.16-rcX regression that I reported few weeks > > ago. I applied it and verified that Dell R640 server that I mentioned > > in the bug report boots up and the disk works. > > Artem (or anyone else), what's the status here? I have this on my list > of regressions, but it looks like there wasn't any progress in the past > week. Or was it discussed somewhere else or even fixed in the meantime > and I missed it? Ciao, Thorsten Hi, it is not fixed in upstream. I got an e-mail from James that the fixes are in his tree in the "fixes" branch. There is no word about when it will be merged. There is also no stable tag.