| To: | Jens Axboe <axboe@xxxxxxx> |
|---|---|
| Subject: | Re: The XFS real-time subvolume in Linux |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Wed, 5 Oct 2005 17:10:36 +0200 |
| Cc: | Eric Sandeen <sandeen@xxxxxxx>, Steve Lord <lord@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20051005145808.GC3511@suse.de> |
| References: | <BAY110-F272BEC2E5C429160FB4068B4830@phx.gbl> <200510051624.16213.ak@suse.de> <20051005145808.GC3511@suse.de> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.8.2 |
On Wednesday 05 October 2005 16:58, Jens Axboe wrote: > There are still unknowns, the HD still being the biggest one of course. > The problem is that you don't know the worst case HD performance, it > might be doing all sorts of rewriting, calibration, error correct etc > that can still screw you. So I think without definitely knowledge of > what the HD will do in case of errors (or a way to control that which > you definitely can on some drives), it's still pretty hazy. It gets > better, but if you are looking for complete guarantees I don't think > it's good enough. Yes, but GRIO has exactly the same problem. I assume they need custom calibration for each IO subsystem. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: The XFS real-time subvolume in Linux, Jens Axboe |
|---|---|
| Next by Date: | Re: The XFS real-time subvolume in Linux, Jens Axboe |
| Previous by Thread: | Re: The XFS real-time subvolume in Linux, Jens Axboe |
| Next by Thread: | Re: The XFS real-time subvolume in Linux, Jens Axboe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |