> > Congratulations, Bart! Bug fixed indeed - just tried. But I keep thinking > > that the right place for the far fnodes is the HMA > > Done that too :) > > I was thinking how to give the user the choice. But the these fnodes are > to mostly disappear anyway so to fiddle with config.sys syntax wasn't > really worth it... So they just go high into the HMA if HMA is available, > else low, just like the buffers.
so user who is stupid enough to specify DOS=LOW,UMB suffers the consequence (of no HMA being available) by loading fnodes into conventional memory even though they potentially could be loaded into UMB's (except the 2 you keep in conventional memory). what if not all fnodes could be stored in HMA. then part of fnodes stored in HMA and remaining in conventional memory? or a first-fit (easier than splitting up ) by first check HMA, then UMB, then falling back to conv. memory ?: 0a) put 2 fnodes in conventional RAM. 0b) set files to max(requested_files_amount , minimum_files_amount) 0c) set total number of inodes to this files amount 1)if all fnodes (except maybe 2) fit entirely in available free HMA space, put them there. else 2)if all fnodes (except maybe 2) fit entirely in available free UMB space, put them there otherwise 3)put all fnodes in conventional memory. // files=250 might fail for 1) for example, but succeed for 2) and very probably succeeds for 3) (250 fnodes * 66 bytes per fnode = 16500bytes). do ALL fnodes fit in scenario 3? for example on a 8086 with 128KB RAM? if not, reduce? but how far? Bernd ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
