From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-xc44.google.com (mail-yw1-xc44.google.com [IPv6:2607:f8b0:4864:20::c44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0DB0621157438 for ; Wed, 26 Sep 2018 14:53:10 -0700 (PDT) Received: by mail-yw1-xc44.google.com with SMTP id v1-v6so233882ywv.6 for ; Wed, 26 Sep 2018 14:53:10 -0700 (PDT) Date: Wed, 26 Sep 2018 14:53:07 -0700 From: Tejun Heo Subject: Re: [RFC workqueue/driver-core PATCH 1/5] workqueue: Provide queue_work_near to queue work near a given NUMA node Message-ID: <20180926215307.GA270328@devbig004.ftw2.facebook.com> References: <20180926214433.13512.30289.stgit@localhost.localdomain> <20180926215138.13512.33146.stgit@localhost.localdomain> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20180926215138.13512.33146.stgit@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Alexander Duyck Cc: len.brown@intel.com, linux-pm@vger.kernel.org, gregkh@linuxfoundation.org, linux-nvdimm@lists.01.org, jiangshanlai@gmail.com, linux-kernel@vger.kernel.org, zwisler@kernel.org, pavel@ucw.cz, rafael@kernel.org, akpm@linux-foundation.org List-ID: Hello, On Wed, Sep 26, 2018 at 02:51:38PM -0700, Alexander Duyck wrote: > This patch provides a new function queue_work_near which is meant to > schedule work on the nearest unbound CPU to the requested NUMA node. The > main motivation for this is to help assist asynchronous init to better > improve boot times for devices that are local to a specific node. > > Signed-off-by: Alexander Duyck Why not just use unbound workqueues, which are NUMA-affine by default? Are there big enough advantages? Thanks. -- tejun _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5571CC43382 for ; Wed, 26 Sep 2018 21:53:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E8E9D2154B for ; Wed, 26 Sep 2018 21:53:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="kTpWKcug" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E8E9D2154B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726651AbeI0EIK (ORCPT ); Thu, 27 Sep 2018 00:08:10 -0400 Received: from mail-yw1-f66.google.com ([209.85.161.66]:42998 "EHLO mail-yw1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726489AbeI0EIK (ORCPT ); Thu, 27 Sep 2018 00:08:10 -0400 Received: by mail-yw1-f66.google.com with SMTP id h134-v6so225845ywc.9; Wed, 26 Sep 2018 14:53:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=dbJ9dw+j5Fkdnr648wIBTx+ZdirZClkdxE7IVB+KI3o=; b=kTpWKcugsz2WSk5J/CMOQfhXs41y/nv/oGhWf9ciPS2qcDGSpN5x7jYFGXhMxFtBOD LoXoQKsKlka4NYpDYz6Q2Qpi6Ho5/Q78KtgC/NQSGHhRCmDu1kXemZh98cVu0d8iN467 bhrIk7q92kOWCg7zRX9MPIjE9jag0FEDlXEt2rmAKm5TArhBv8+aSm31GaDyaz3qpQBJ z38IYC2AfJPZCRKDDSwnYRmXs4RQpkbbb3TO2Kam8JhFFv7b/dNDnkjs/4c359RUSVmo tkr47jcPyNd0omnqFggDTTQX2/HbTc77exT+emHnMLSIOWDezBbdVWMD2RpR2mH6+Vy9 TEPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=dbJ9dw+j5Fkdnr648wIBTx+ZdirZClkdxE7IVB+KI3o=; b=pfHEzBnuDQLR0dzC5t052oruuO24PmTlb0hUQbQicQd1ubkJU9z/xy+PpBbwp2kxWL M6ZEJgqkrTc2KmFhxDMxzSx3Y2Rdcb1llmo5na60O2dGQLvdlWghmG+w3voQ4Ao7aig8 c/T8CTVJqHNQD49JplV0x2PNWPbWQANlIbYPehsmu4CDusohAsDkhNaqbpdoVaxOjM5z zVgAOCfbqRDeIyh2xITIyiuC9SStobfvZhZISsU6+2pfJihDG6lM1/behTLCh5FEzzNg 8PQgFZ73+DmWGQoYKh8y7nLiZgoFB/jEwT51qOfyCvHDtt9FYwJ3kEcu6HWFiS6dxpEa gx3g== X-Gm-Message-State: ABuFfogA4zKTONMsOU7c9Wcinq7zG3I34whEpCByMumtyzMsrotTdfaS sZdAbiZp95ABwo+ynPclUTE= X-Google-Smtp-Source: ACcGV60AGhy3FVY1NMHadLhh14mt2L9rARTv81Jrst9WuKheOGEDdiDj9TU5LLksjYgqEi6KJt2V+w== X-Received: by 2002:a81:31cc:: with SMTP id x195-v6mr4119034ywx.502.1537998789899; Wed, 26 Sep 2018 14:53:09 -0700 (PDT) Received: from localhost ([2620:10d:c091:200::4:2c77]) by smtp.gmail.com with ESMTPSA id k2-v6sm147812ywh.52.2018.09.26.14.53.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Sep 2018 14:53:09 -0700 (PDT) Date: Wed, 26 Sep 2018 14:53:07 -0700 From: Tejun Heo To: Alexander Duyck Cc: linux-nvdimm@lists.01.org, gregkh@linuxfoundation.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, len.brown@intel.com, dave.jiang@intel.com, rafael@kernel.org, vishal.l.verma@intel.com, jiangshanlai@gmail.com, pavel@ucw.cz, zwisler@kernel.org, dan.j.williams@intel.com Subject: Re: [RFC workqueue/driver-core PATCH 1/5] workqueue: Provide queue_work_near to queue work near a given NUMA node Message-ID: <20180926215307.GA270328@devbig004.ftw2.facebook.com> References: <20180926214433.13512.30289.stgit@localhost.localdomain> <20180926215138.13512.33146.stgit@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180926215138.13512.33146.stgit@localhost.localdomain> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Wed, Sep 26, 2018 at 02:51:38PM -0700, Alexander Duyck wrote: > This patch provides a new function queue_work_near which is meant to > schedule work on the nearest unbound CPU to the requested NUMA node. The > main motivation for this is to help assist asynchronous init to better > improve boot times for devices that are local to a specific node. > > Signed-off-by: Alexander Duyck Why not just use unbound workqueues, which are NUMA-affine by default? Are there big enough advantages? Thanks. -- tejun From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [RFC workqueue/driver-core PATCH 1/5] workqueue: Provide queue_work_near to queue work near a given NUMA node Date: Wed, 26 Sep 2018 14:53:07 -0700 Message-ID: <20180926215307.GA270328@devbig004.ftw2.facebook.com> References: <20180926214433.13512.30289.stgit@localhost.localdomain> <20180926215138.13512.33146.stgit@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20180926215138.13512.33146.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" To: Alexander Duyck Cc: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org, linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org, jiangshanlai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, zwisler-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, pavel-+ZI9xUNit7I@public.gmane.org, rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org List-Id: linux-pm@vger.kernel.org Hello, On Wed, Sep 26, 2018 at 02:51:38PM -0700, Alexander Duyck wrote: > This patch provides a new function queue_work_near which is meant to > schedule work on the nearest unbound CPU to the requested NUMA node. The > main motivation for this is to help assist asynchronous init to better > improve boot times for devices that are local to a specific node. > > Signed-off-by: Alexander Duyck Why not just use unbound workqueues, which are NUMA-affine by default? Are there big enough advantages? Thanks. -- tejun