From: Mike Galbraith <mgalbraith@suse.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Brian Bloniarz <bmb@athenacr.com>, Chris Wedgwood <cw@f00f.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Jef Driesen <jefdriesen@telenet.be>,
linux-kernel@vger.kernel.org
Subject: Re: Slow pty's (was Re: libdivecomputer interfaces?)
Date: Thu, 17 Jun 2010 08:39:30 +0200 [thread overview]
Message-ID: <1276756770.8248.20.camel@marge.simson.net> (raw)
In-Reply-To: <1276701411.30669.6.camel@marge.simson.net>
On Wed, 2010-06-16 at 17:16 +0200, Mike Galbraith wrote:
> On Wed, 2010-06-16 at 17:03 +0200, Jiri Kosina wrote:
> > On Thu, 10 Jun 2010, Brian Bloniarz wrote:
> >
> > > On 06/10/2010 02:10 PM, Chris Wedgwood wrote:
> > > > (sorry if this reponse isn't on target, i was just pointed to this
> > > > thread a few minutes ago)
> > > >
> > > >
> > > > On Thu, Jun 10, 2010 at 10:25:36AM -0700, Linus Torvalds wrote:
> > > >
> > > >> I thought we long since (ie back last fall) fixed the latency
> > > >> problems with pty's, but there does seem to be something very fishy
> > > >> going on there still.
> > > >
> > > > this might not be related, but i have slow serial ports with NOHZ that
> > > > goes away when i revert 39c0cbe2150cbd848a25ba6cdb271d1ad46818ad.
> > >
> > > Unrelated or not, I think Chris is right about this. Somewhere before
> > > -rc1, the emulated serial console on my KVM instance became slow
> > > to echo input. I just tested with the commit reverted and it's
> > > back to normal.
> >
> > So let's CC Mike then.
>
> Chris already gave me a heads up, it's on my todo. The old P4 box I use
> for a serial console box is exploding on boot, or I would have already
> had a look.
(Removing filth and re-seating ram seems to have revived poor old P4)
I'm not seeing any problem with serial console here, seems to work just
fine P4->Q6600, both running NOHZ kernels with nohz_ratelimit(), 33.5 on
the P4, and tip.today on the Q6600.
Eyeballing it, perhaps we need to proceed downward if any needs_cpu
condition is true, despite having just been here a wee bit ago.
Does this help anyone's woes?
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 5f171f0..ec72fad 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -262,7 +262,7 @@ void tick_nohz_stop_sched_tick(int inidle)
ktime_t last_update, expires, now;
struct clock_event_device *dev = __get_cpu_var(tick_cpu_device).evtdev;
u64 time_delta;
- int cpu;
+ int cpu, cpu_needed;
local_irq_save(flags);
@@ -315,7 +315,9 @@ void tick_nohz_stop_sched_tick(int inidle)
goto end;
}
- if (nohz_ratelimit(cpu))
+ cpu_needed = rcu_needs_cpu(cpu) || printk_needs_cpu(cpu) || arch_needs_cpu(cpu);
+
+ if (!cpu_needed && nohz_ratelimit(cpu))
goto end;
ts->idle_calls++;
@@ -327,8 +329,7 @@ void tick_nohz_stop_sched_tick(int inidle)
time_delta = timekeeping_max_deferment();
} while (read_seqretry(&xtime_lock, seq));
- if (rcu_needs_cpu(cpu) || printk_needs_cpu(cpu) ||
- arch_needs_cpu(cpu)) {
+ if (cpu_needed) {
next_jiffies = last_jiffies + 1;
delta_jiffies = 1;
} else {
next prev parent reply other threads:[~2010-06-17 6:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:25 Linus Torvalds
2010-06-10 18:07 ` OGAWA Hirofumi
2010-06-10 18:10 ` Chris Wedgwood
2010-06-10 22:25 ` Brian Bloniarz
2010-06-10 22:30 ` Linus Torvalds
2010-06-16 15:03 ` Jiri Kosina
2010-06-16 15:16 ` Mike Galbraith
2010-06-17 6:39 ` Mike Galbraith [this message]
2010-06-17 7:00 ` Mike Galbraith
2010-06-17 10:50 ` Mike Galbraith
2010-06-17 13:24 ` Peter Zijlstra
2010-06-17 14:11 ` Thomas Gleixner
2010-06-17 14:14 ` Mike Galbraith
2010-06-17 14:56 ` Brian Bloniarz
2010-06-17 16:02 ` [PATCH] nohz: Fix nohz ratelimit Peter Zijlstra
2010-06-17 17:39 ` [tip:timers/urgent] " tip-bot for Peter Zijlstra
2010-11-12 18:45 ` Slow pty's (was Re: libdivecomputer interfaces?) Jef Driesen
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=1276756770.8248.20.camel@marge.simson.net \
--to=mgalbraith@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bmb@athenacr.com \
--cc=cw@f00f.org \
--cc=gregkh@suse.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jefdriesen@telenet.be \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome