From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Jiri Slaby <jslaby@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tty: Use unbound workqueue for all input workers
Date: Sat, 17 Oct 2015 21:32:14 -0700 [thread overview]
Message-ID: <20151018043214.GA9092@kroah.com> (raw)
In-Reply-To: <1445114184-4022-2-git-send-email-peter@hurleysoftware.com>
On Sat, Oct 17, 2015 at 04:36:24PM -0400, Peter Hurley wrote:
> The commonly accepted wisdom that scheduling work on the same cpu
> that handled interrupt i/o benefits from cache-locality is only
> true if the cpu is idle (since bound kworkers are often the highest
> vruntime and thus the lowest priority).
>
> Measurements of scheduling via the unbound queue show lowered
> worst-case latency responses of up to 5x over bound workqueue, without
> increase in average latency or throughput.
>
> pty i/o test measurements show >3x (!) reduced total running time; tests
> previously taking ~8s now complete in <2.5s.
Wow, nice job with this, that's unexpected.
greg k-h
prev parent reply other threads:[~2015-10-18 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 20:36 [PATCH 1/2] tty: Abstract tty buffer work Peter Hurley
2015-10-17 20:36 ` [PATCH 2/2] tty: Use unbound workqueue for all input workers Peter Hurley
2015-10-18 4:32 ` Greg Kroah-Hartman [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=20151018043214.GA9092@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/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