Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1278943pxj; Wed, 19 May 2021 02:21:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwCzgptyy5l1mhbFY3e7zGNWP77iN95aFeY4Rja3steCTCAwr1PpaH07zckQ5WwVoyPugv8 X-Received: by 2002:a92:c7a1:: with SMTP id f1mr9831747ilk.85.1621416066814; Wed, 19 May 2021 02:21:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621416066; cv=none; d=google.com; s=arc-20160816; b=eUF4O2V6on6qgrRYmVpn5O79GDjxfu8tz6Kjs0TzlGPMD1F4xh6nx779jKQd/vrVaX sYSzV91tyr5HDnbtna4paoiJtEunijhigBCRcmZqXoIhgtzvKt1Vm8VScDigvz5F6Zww PxYDvoqFQh6ynBjlIHeUBXnXajZMPOyNThfY8p1016i9nC/+EfV/ms4ASWxyHU6u2Xyw FjVnBtgLhhZS8ptc44nFuPCCZwg381CshYSqLhWLuOqQZ2Vdc8AhA9cLib58yDVX2nB6 9WzvBRypSjw8mRKQRhHqklLV1oOCXJ3vZaQhX8uDrXMgdtRJ2467L39sp+W6NvH8yTmE 4o/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=1CFhwAdeADWfjY+TeEUXI0dttR2qRWxmhTMkaKMBCuk=; b=V80IcWLRWEcB7sD3/ORMiAvCI3UOvgCoIXzimKJClGdDA0lwB+YjY1F2utqFodoSKR yiCKXlX08yGt8IsiQHCm8Avmm/jEht7oNAsK5piLhBnJ3ylUGW6UGeiI2Th6kuZLoylN D3QgKMzeUjqwfeOGyR+c8SKMcdJHtlKvpFx0isP2oUMhpSVcS7gmoYOI4E21VM7VOskM p+Y0/XKevOJdtjQd1YqBm50on5bRwp4VwOLK1QzRAGqzwoeD4vp+oS2X4pBdC1r7I4VG uSaL9sivyDx8SXZV+Sw7wNakH3a2FoNp1yOcYRDmm0GAE3s6/v9K1Y/VP8aG/saSFcw7 O6+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UYZaEetO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d25si2256017jam.64.2021.05.19.02.20.54; Wed, 19 May 2021 02:21:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UYZaEetO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344764AbhERAYj (ORCPT + 99 others); Mon, 17 May 2021 20:24:39 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:29296 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238215AbhERAYh (ORCPT ); Mon, 17 May 2021 20:24:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621297400; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1CFhwAdeADWfjY+TeEUXI0dttR2qRWxmhTMkaKMBCuk=; b=UYZaEetOebS9zOWu1FUz6LGrN+u/Tw0wjudDwjeHlvrZRWwTYwZG/+maG0ai0yZfc0dB5l DBkmUdaC2lHxEdaPMSiMfXC+/QTb6KpVyPwsU88j8m2v4Qp1u5yqL1JEhXYRsBaQzmKWrS zYPduMi7BE4J9WnNFqHsdM2efYd3Wms= Received: from mail-lj1-f198.google.com (mail-lj1-f198.google.com [209.85.208.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-474-jFp36KDaOu-lvhnaHAxoFg-1; Mon, 17 May 2021 20:23:18 -0400 X-MC-Unique: jFp36KDaOu-lvhnaHAxoFg-1 Received: by mail-lj1-f198.google.com with SMTP id h1-20020a2e9ec10000b02900edf305c2e1so3857626ljk.12 for ; Mon, 17 May 2021 17:23:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1CFhwAdeADWfjY+TeEUXI0dttR2qRWxmhTMkaKMBCuk=; b=KnwORj8fnXFDD/PxdDdMJI5NCMuvNMAsMskU1wlDquYVflDM1dfwbL7McX1v0bvn4D 1gp6NyWy3dD7KeX8FFM11YCIQQ+gHxGXJDHEJCoWc1tcak0IMnbPqGRnwIdhLBYEPvpl vtnZ3b30127+YlOhnnqFFZwxnpCRIgPSyDUjdRJE8wPMCEmlU4thkYNdW90gRjh+y6BW j8hpBA1JWk6+rsntAmMD3PrCjNMsKv9p7Iu6sKR/rCdDAFizzxacJGXUt7D0cxWq9Dlp h5KHW31ime7IeX9ZvEJz3ftQD+sQ/hHrHWyVB/Db1hEuuHLSrzdtzaUJo78Ni0cOg+VJ QRCw== X-Gm-Message-State: AOAM532BfxFQIccqETQIN7EzyusqopSzUpkniKPfqKxJqLo0Xw4G5Pli dmHZnyehjTWv8QB+nP5a4caP2SrWKWRwVBzMg4dvxWWhCODrv64phgjOf9D9klNxJDlHek1QxvO pEpMsY1M3s0r3dZYe/JLjN3FxjGtnIX1FIoghBlPB X-Received: by 2002:a05:6512:3da1:: with SMTP id k33mr1954929lfv.114.1621297396825; Mon, 17 May 2021 17:23:16 -0700 (PDT) X-Received: by 2002:a05:6512:3da1:: with SMTP id k33mr1954902lfv.114.1621297396624; Mon, 17 May 2021 17:23:16 -0700 (PDT) MIME-Version: 1.0 References: <20210504092340.00006c61@intel.com> <87pmxpdr32.ffs@nanos.tec.linutronix.de> <87im3gewlu.ffs@nanos.tec.linutronix.de> In-Reply-To: <87im3gewlu.ffs@nanos.tec.linutronix.de> From: Nitesh Lal Date: Mon, 17 May 2021 20:23:05 -0400 Message-ID: Subject: Re: [PATCH tip:irq/core v1] genirq: remove auto-set of the mask when setting the hint To: Thomas Gleixner Cc: Jesse Brandeburg , Robin Murphy , Ingo Molnar , linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, jbrandeb@kernel.org, "frederic@kernel.org" , "juri.lelli@redhat.com" , Marcelo Tosatti , Alex Belits , "linux-api@vger.kernel.org" , "bhelgaas@google.com" , "linux-pci@vger.kernel.org" , "rostedt@goodmis.org" , "peterz@infradead.org" , "davem@davemloft.net" , "akpm@linux-foundation.org" , "sfr@canb.auug.org.au" , "stephen@networkplumber.org" , "rppt@linux.vnet.ibm.com" , "jinyuqi@huawei.com" , "zhangshaokun@hisilicon.com" , netdev@vger.kernel.org, chris.friesen@windriver.com, Marc Zyngier , Neil Horman , pjwaskiewicz@gmail.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 17, 2021 at 8:04 PM Thomas Gleixner wrote: > > On Mon, May 17 2021 at 18:44, Nitesh Lal wrote: > > On Mon, May 17, 2021 at 4:48 PM Thomas Gleixner wrote: > >> The hint was added so that userspace has a better understanding where it > >> should place the interrupt. So if irqbalanced ignores it anyway, then > >> what's the point of the hint? IOW, why is it still used drivers? > >> > > Took a quick look at the irqbalance repo and saw the following commit: > > > > dcc411e7bf remove affinity_hint infrastructure > > > > The commit message mentions that "PJ is redesiging how affinity hinting > > works in the kernel, the future model will just tell us to ignore an IRQ, > > and the kernel will handle placement for us. As such we can remove the > > affinity_hint recognition entirely". > > No idea who PJ is. I really love useful commit messages. Maybe Neil can > shed some light on that. > > > This does indicate that apparently, irqbalance moved away from the usage of > > affinity_hint. However, the next question is what was this future > > model? > > I might have missed something in the last 5 years, but that's the first > time I hear about someone trying to cleanup that thing. > > > I don't know but I can surely look into it if that helps or maybe someone > > here already knows about it? > > I CC'ed Neil :) Thanks, I have added PJ Waskiewicz as well who I think was referred in that commit message as PJ. > > >> Now there is another aspect to that. What happens if irqbalanced does > >> not run at all and a driver relies on the side effect of the hint > >> setting the initial affinity. Bah... > >> > > > > Right, but if they only rely on this API so that the IRQs are spread across > > all the CPUs then that issue is already resolved and these other drivers > > should not regress because of changing this behavior. Isn't it? > > Is that true for all architectures? Unfortunately, I don't know and that's probably why we have to be careful. -- Nitesh