On Wed, 9 April 2008 23:09:07 +0200, Pavel Machek wrote:If someone implemented readpages(), that might be possible - depending on your definition of 'reasonable' and your workload. Writes will hit the disk roughly in order. When readahead requests a bunch of pages, there is some chance of them being adjacent and having the block layer combine most of the bios into a few large ones. The main drawbacks are: - No reservations. If data is written in random order or several writers chew away in parallel, write order will be fairly pessimal. - No readahead yet. Wouldn't be hard to do. - Garbage collection completely ignores fragmentation. If segments are needed and one contains a nice long extend from a single file, that data will be written elsewhere, often split between two segments. Rinse, repeat and fragmentation will increase over time. - File creation/deletion currently will cause disk heads to jump in triangles. This hurts write performance on most flash media as well, so it will get changed reasonably soon. All of those are solvable. Some will definitely be solved because the help performance on flash media as well. Other may or may not. Jörn -- When people work hard for you for a pat on the back, you've got to give them that pat. -- Robert Heinlein --
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Alan Stern | Re: 2.6.22-rc2-mm1 |
| Satyam Sharma | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
| William Lee Irwin III | Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] |
git: | |
| Dale Farnsworth | Re: [PATCH 03/39] mv643xx_eth: shorten reg names |
| Jarek Poplawski | Re: HTB accuracy for high speed |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
