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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 4 Apr 2009 22:18:20 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [GIT PULL] Ext3 latency fixes


* Jens Axboe <jens.axboe@...cle.com> wrote:

> > Quite frankly, the fact that I can see _seconds_ of latencies 
> > with a really good SSD is not acceptable. The fact that it is by 
> > design is even less so.
> 
> Agree, multi-second latencies is not acceptable.

btw., just to insert some hard data: usability studies place the 
acceptance threshold for delays to around 300 milliseconds.

If the computer does not 'respond' (in a real or a fake, visible or 
audible way) to their input within 0.3 seconds they get annoyed 
emotionally.

It does not matter how complex it is for the kernel to solve this 
problem, it does not matter how far away and difficult to access the 
data is. If we are not absolutely latency centric in Linux, if we 
spuriously delay apps that do supposedly simple-looking things the 
user _will_ get annoyed and _will_ pick another OS.

All things considered it is certainly a combined kernel and app 
problem space to get there, but not being completely aware of its 
importance in the kernel kills any chance of us ever having a 
long-term solution.

	Ingo
--
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