|
|
Post by pharrisire on Nov 25, 2010 9:23:27 GMT -5
What is /does
" Flowtable cleaner started " ?
Was that in KNOS1 and 2 and I never noticed?
or is this something new?
|
|
|
|
Post by Kevin McAleavey on Nov 27, 2010 2:08:27 GMT -5
What is /does " Flowtable cleaner started " ? Was that in KNOS1 and 2 and I never noticed? or is this something new? Yes indeed! We had a handful of people for whom KNOS failed to boot, and now that we're ready to go with an "official release" hopefully in the spring for use by "regular folks" we wanted to invite those for whom KNOS didn't work in our previous two betas to either get it to boot successfully with all the fixes BSD did for our kernel, or ... should it STILL fail to boot for them, or just died ... be able to get a screenshot or an email back from anyone who had a problem with KNOS booting to have some useful information for us to pass back to the BSD kernel folks so that whatever might have caused that to get fixed. "Flowtable cleaner" is a part of the kernel that sits in wait while the kernel tries to identify each chip on any computer's motherboard, find out how to talk to it, and what if anything else on the particular motherboard might pose a bottleneck or problem that needs to be worked around before finally "marshalling" all of the kernel and the video stuff to bring a happy and reliable KNOS up onto their screen. Flowtable works like an old-fashioned telephone switchboard once it has amassed details on each piece of hardware and then "wires up" how the kernel intends to communicate with all that hardware by the most direct and efficient route possible. The "flowtable" is an internal kernel database of who to talk to and who to go around on that motherboard to communicate as fast as possible with whatever it is handed on any particular machine. |
|
|
|
Post by pharrisire on Nov 27, 2010 10:50:07 GMT -5
Thanks
|
|
