On Tue, 2005-03-01 at 15:38, Andi Kleen wrote: > Arjan van de Ven <[EMAIL PROTECTED]> writes: > > > > You want to *use* the kernel pagecache as much as you can. You do so by > > using mmap and such, and msync to force content to disk. That uses the > > Last time I checked you couldn't mmap block devices. Has this changed > now? Could be a problem for an iSCSI target. > we definitely need to support export any block device like lv or md, or just regular hdX or sdX.
we also need supports to act as an iSCSI bridge mode, which means it can export real scsi devices. ming > I remember there used to be a hack in 2.2 to map them to a pseudo fs > to allow mmaping, but that's not very nice and would require > another step by the administrator. > > Also using mmap would imply the server only works on 64bit systems, > and may even there have uncomfortable limits. One issue is that > the kernel currently doesn't garbage collect page tables, so > e.g. when you map a 10TB volume this way and the user accesses > it randomly you will eventually have quite a lot of page tables > filling up your RAM. And those will not go away. > > My overall feeling is that mmap is not a good idea for this. > > -Andi > - > 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 - 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
