| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: XFS/Tux readahead setting??? |
| From: | Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx> |
| Date: | Wed, 5 Dec 2001 18:48:25 +0100 (CET) |
| Cc: | XFS Mailing list <linux-xfs@xxxxxxxxxxx>, Tux mailing list <tux-list@xxxxxxxxxx> |
| In-reply-to: | <1007573249.22679.20.camel@jen.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
> And last time this came up, you could not change the application, > correct? Otherwise I would say use O_DIRECT in XFS to do the reads, > and use threads in the application to do explicit readahead into > buffers. > > Try bumping up the max and see what happens, but I think a lot of the > lower layers will automatically split it again, I don't think the IDE > code goes bigger than 128K anyway. I'm currently using the tux web server, and I really don't know how to tell it to read the next - say - 4 megs of the file. I'd be glad if this could be settable in the kernel... -- Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA Computers are like air conditioners. They stop working when you open Windows. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE - strip nearly all #ifdef __sgi code from dmapi, Dean Roehrich |
|---|---|
| Next by Date: | Re: Files on XFS not safe?!, Xianglong Yuan |
| Previous by Thread: | Re: XFS readahead setting???, Steve Lord |
| Next by Thread: | TAKE - strip nearly all #ifdef __sgi code from dmapi, Dean Roehrich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |