On Tue, 2005-03-01 at 14:01, Vikas Aggarwal wrote: > And If future IET be visioned as an Enterprise Class Array(Multiple > Host-Side Adapters ie., FAs + Multiple Device Side Adapters ie., DAs), > should better be in direct control of all the system-resources without > being pushed out the kernel. > of course this is the reason why we use that name.
ming > Bryan Henderson <[EMAIL PROTECTED]> wrote: > One thing that's implicit in your reasons for wanting to be in > the kernel > is that you've chosen to exploit the kernel's page cache. As a > user of > the page cache, you have more control from inside the kernel > than from > user space. The page cache was designed to be fundamentally > invisible to > user space. > > A pure user space implementation of an ISCSI target would use > process > virtual memory for a cache and manage it itself. It would > access the > storage with direct I/O. It looks to me like this is aimed at > a > single-application Linux system (the whole system is just an > ISCSI > target), which means there's not much need for a kernel to > manage shared > resources. > > -- > Bryan Henderson IBM Almaden Research Center > San Jose CA Filesystems > > > ------------------------------------------------------- > SF email is sponsored by - The IT Pro duct Guide > Read honest & candid reviews on hundreds of IT Products from > real users. > Discover which products truly live up to the hype. Start > reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Iscsitarget-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel > > ______________________________________________________________________ > Do you Yahoo!? > Read only the mail you want - Yahoo! Mail SpamGuard. - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
