From: Chris Metcalf <cmetcalf@tilera.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Fr?d?ric Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL, RFC] Full dynticks, CONFIG_NO_HZ_FULL feature
Date: Wed, 8 May 2013 14:14:44 -0400 [thread overview]
Message-ID: <518A9614.2010805@tilera.com> (raw)
In-Reply-To: <CA+55aFxYRDZvisB7iZ5a-bcp5_2pkvcC9Opk6=yJtjfK57EWTw@mail.gmail.com>
On 5/6/2013 3:32 PM, Linus Torvalds wrote:
> On Mon, May 6, 2013 at 8:35 AM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
>>>
>>> I think Linus might have referred to my 'future plans' entry:
>
> Indeed. I feel that HPC is entirely irrelevant to anybody,
> *especially* HPC benchmarks. In real life, even HPC doesn't tend to
> have the nice behavior their much-touted benchmarks have.
>
> So as long as the NOHZ is for HPC-style loads, then quite frankly, I
> don't feel it is worth it. The _only_ thing that makes it worth it is
> that "future plans" part where it would actually help real loads.
The work is very relevant to a lot of the actual customer applications
that Tilera chips are sold into: running very low latency userspace
applications that handle packet processing (or, to a lesser extent,
video frame processing). For packet processing in particular, you really
want to be able to guarantee that you can set up a core handling packets
in userspace and get NO INTERRUPTS at all, ever. If you do get an
interrupt, you end up dropping a bunch of packets on the floor.
We are still using code I developed internally for this (for the curious,
in my dataplane branch on kernel.org), but I expect in the relatively near
future we will be trying to switch to the NOHZ stuff instead. I'm
really pleased to see it start getting merged up.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
prev parent reply other threads:[~2013-05-08 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 11:03 [GIT PULL, RFC] Full dynticks, CONFIG_NO_HZ_FULL feature Ingo Molnar
2013-05-05 20:33 ` Linus Torvalds
2013-05-05 21:25 ` Paul E. McKenney
2013-05-06 9:25 ` Ingo Molnar
2013-05-06 15:35 ` Paul E. McKenney
2013-05-06 19:32 ` Linus Torvalds
2013-05-07 6:43 ` Ingo Molnar
2013-05-08 18:14 ` Chris Metcalf [this message]
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=518A9614.2010805@tilera.com \
--to=cmetcalf@tilera.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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