| To: | stan@xxxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Questions about XFS |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Sat, 26 Oct 2013 22:29:06 -0500 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <526B9C55.9000707@xxxxxxxxxxxxxxxxx> |
| References: | <CAD+1EGPG1G9Q8kwaSUjxVjvx73UByLb3G0rmUbgJr+zD-CnjEw@xxxxxxxxxxxxxx> <20131025164255.46d2829c@xxxxxxxxxxxxxxxxxxxx> <526A86F2.9070400@xxxxxxxxxxx> <526B9C55.9000707@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 |
On 10/26/13 5:41 AM, Stan Hoeppner wrote: > On 10/25/2013 9:57 AM, Eric Sandeen wrote: > >> allocator, but it doesn't have GRIO (Guaranteed Realtime I/O) like >> IRIX does. > > Wasn't it called "Guaranteed-Rate I/O"? Yeah, you are right. Brain fart. > And required the Origin ccNUMA > hardware including the HUB and XBow ASICs? IIRC this had no real-time > guarantee, but simply reserved X amount of bandwidth from the XBow > through the HUB to the processor, and finally the kernel and process. > Whether the attached disks could sustain the reserved bandwidth was > another matter. There were 2 versions, implemented in very different ways... Anyway, if Harry would "prefer designing and implementing" it for Linux, I'll just let him get started. :) -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Photo Retouching Services - Photo Cut Out - Photo Editing, Kevin |
|---|---|
| Next by Date: | Re: [PATCH] xfs: prevent stack overflows from page cache allocation, Dave Chinner |
| Previous by Thread: | Re: Questions about XFS, Stan Hoeppner |
| Next by Thread: | Re: Questions about XFS, harryxiyou |
| Indexes: | [Date] [Thread] [Top] [All Lists] |