lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100924123901.243c85e1@jbarnes-desktop>
Date:	Fri, 24 Sep 2010 12:39:01 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Vasily Khoruzhick <anarsoul@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Sitsofe Wheeler <sitsofe@...oo.com>,
	Venkatesh Pallipadi <venki@...gle.com>,
	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	Len Brown <lenb@...nel.org>
Subject: Re: Interrupt latency on some 945GM platforms

On Thu, 16 Sep 2010 23:06:46 +0300
Vasily Khoruzhick <anarsoul@...il.com> wrote:

> В сообщении от 16 of September 2010 21:50:50 автор Thomas Gleixner написал:
> > Ok. The problematic part of HPET was not the clocksource, it was the
> > clock event device which failed to deliver interrupts occasionally. It
> > was worth a try at least.
> 
> Hm, it seems that jerky glxgears is not related to jerky keyboard events. 
> Keyboard is jerky only in konsole (kde terminal emulator), it seems something 
> happened it seems that font rendering performance is much worse in latest 
> xf86-video-intel than in xf86-video-intel-2.12.0.

Len just had me try a few things too:
  - maxcpus=1 lets things work
  - offlining cpu1 at runtime (echo 0
    > /sys/devices/system/cpu/cpu1/online) lets things work
  - binding the i915 interrupt to cpu 0 does *not* help

Vasily and Paolo, do you both have Atom CPUs with hyperthreading
enabled?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ