From: Chris Metcalf <cmetcalf@ezchip.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nohz: prevent tilegx network driver interrupts
Date: Mon, 20 Jul 2015 17:22:12 -0400 [thread overview]
Message-ID: <55AD6684.3080607@ezchip.com> (raw)
In-Reply-To: <20150711143033.GE10257@lerouge>
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.
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
next prev parent reply other threads:[~2015-07-20 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 17:33 [PATCH] nohz: prevent tilegx network driver interrupts Chris Metcalf
2015-07-10 18:24 ` Frederic Weisbecker
2015-07-10 19:05 ` Chris Metcalf
2015-07-10 19:37 ` [PATCH v2] " Chris Metcalf
2015-07-10 22:45 ` Josh Cartwright
2015-07-10 23:06 ` Chris Metcalf
2015-07-10 23:12 ` Josh Cartwright
2015-07-11 14:44 ` Frederic Weisbecker
2015-07-11 15:04 ` Chris Metcalf
2015-07-11 14:30 ` [PATCH] " Frederic Weisbecker
2015-07-20 21:22 ` Chris Metcalf [this message]
2015-07-20 21:49 ` Frederic Weisbecker
2015-07-20 22:15 ` Chris Metcalf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55AD6684.3080607@ezchip.com \
--to=cmetcalf@ezchip.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox