Muli, I well aware of the controversy surrounding FS access from kernel modules and I accept, that in general, kernel modules should be using the FS for storage. However, in essence, I'm using the *wrong* tool for the right job: I shouldn't be using Linux on a i386/x86-64 in the first place; I should be using a network OS with a network chip. However, Linux/x86 uses (relatively) cheap hardware and has massive driver support and a kernel modules is (again, relatively) easy to write and modify. Oh... and Linux is easy to bend :)
After doing some contemplating I decided that I don't really need access to an FS; or actually, all I need a is huge cyclic buffer with fast sequential R/W and force-able sync. If anything the VFS layer will only slow me down. I wonder if the raw character code is code enough to be yanked out and used for this project? Anyways, Thanks. Gilboa On Thu, 2005-07-28 at 23:41 +0300, Muli Ben-Yehuda wrote: > On Thu, Jul 28, 2005 at 04:15:57PM +0300, Gilboa Davara wrote: > > > Never the less, if anyone has interesting insight as for how to .very. > > fast file I/O inside the kernel (Yes, I know that its considered bad, > > and may results from a bad design decision; Linux was never designed > > that way, etc. Umm... sadly (?) enough, porting my code to vxworks is > > not an option ;)) > > Don't... it's counter-intuitive to the way Linux works (which means > you'll have a hard time implementing it, and could very well be better > off rearchitecting it). We used to have a web server in the kernel > until some guys came along and showed that it could be done just as > fast from userspace. > > Cheers, > Muli ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
