linux-kernel - Re: How git affects kernel.org performance

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: <20070109021812.GE44262@sgi.com>
Date:	Mon, 8 Jan 2007 18:18:12 -0800
From:	Jeremy Higdon <jeremy@....com>
To:	Paul Jackson <pj@....com>
Cc:	Jeff Garzik <jeff@...zik.org>, tytso@....edu, suparna@...ibm.com,
	akpm@...l.org, w@....eu, torvalds@...l.org, hpa@...or.com,
	git@...r.kernel.org, nigel@...el.suspend2.net, warthog9@...nel.org,
	randy.dunlap@...cle.com, pavel@....cz,
	linux-kernel@...r.kernel.org, webmaster@...nel.org,
	linux-ext4@...r.kernel.org
Subject: Re: How git affects kernel.org performance

On Mon, Jan 08, 2007 at 05:09:34PM -0800, Paul Jackson wrote:
> Jeff wrote:
> > Something I just thought of:  ATA and SCSI hard disks do their own
> > read-ahead.
> 
> Probably this is wishful thinking on my part, but I would have hoped
> that most of the read-ahead they did was for stuff that happened to be
> on the cylinder they were reading anyway.  So long as their read-ahead
> doesn't cause much extra or delayed disk head motion, what does it
> matter?


And they usually won't readahead if there is another command to
process, though they can be set up to read unrequested data in
spite of outstanding commands.

When they are reading ahead, they'll only fetch LBAs beyond the last
request until a buffer fills or the readahead gets interrupted.

jeremy
-
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/