Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757020AbbGTVtt (ORCPT ); Mon, 20 Jul 2015 17:49:49 -0400 Received: from mail-wg0-f42.google.com ([74.125.82.42]:36565 "EHLO mail-wg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752753AbbGTVtr (ORCPT ); Mon, 20 Jul 2015 17:49:47 -0400 Date: Mon, 20 Jul 2015 23:49:44 +0200 From: Frederic Weisbecker To: Chris Metcalf Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nohz: prevent tilegx network driver interrupts Message-ID: <20150720214943.GC13032@lerouge> References: <1436549624-16104-1-git-send-email-cmetcalf@ezchip.com> <20150710182406.GC26428@lerouge> <55A0175E.2010200@ezchip.com> <20150711143033.GE10257@lerouge> <55AD6684.3080607@ezchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55AD6684.3080607@ezchip.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1691 Lines: 36 On Mon, Jul 20, 2015 at 05:22:12PM -0400, Chris Metcalf wrote: > On 07/11/2015 10:30 AM, Frederic Weisbecker wrote: > >On Fri, Jul 10, 2015 at 03:05:02PM -0400, Chris Metcalf wrote: > >>The tilegx chips typically don't do cpu offlining anyway, since > >>we've never really found a usecase, so whatever you boot with > >>you always have available. We do have support for a bare-metal > >>mode which you can run on some of the cores, so you may start > >>with fewer than cpu_possible actually running, but it will always > >>be that same set of cores. > >And that bare metal mode runs out of Linux? > > The bare metal environment runs on cpus that have been marked > as unavailable to Linux, so Linux just sees them as permanently > offlined. There is a BME driver (which we haven't upstreamed, > since the BME isn't upstreamed either) that arranges to share > memory between the BME and Linux. > > I don't think that many customers are using the BME in any > case. We push all of them towards using our dataplane mode > instead, since it almost always works just as well from a > performance perspective, and is easier to develop code for. So bare metal mode is different than dataplane mode, right? Where bare metal mode offlines the CPU and IIUC dataplane mode instead uses CPUs that are available to Linux, just isolated with nohz and various affinity stuff, right? > -- > Chris Metcalf, EZChip Semiconductor > http://www.ezchip.com > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/