Mark Lobo wrote: > Hello! > > I had a question about disabling the block layer for SCSI devices. We > have an embedded device, and it runs 2.4.30. We need to be able to > support a lot of SCSI devices (in the thousands) for our device, and we > talk to the devices via SG. We are facing a memory allocation problem > after discovering a few thousand devices. For every device, there > seems to be a lot of memory allocated in the block layer. This memory > includes cache memory (which IIRC is reclaimable by the kernel memory > subsystem when it needs it) and also pages that are used for the > alloc_pages pool. > > > > My questions were relating to disabling the block layer for the > devices. We always talk direct passthrough to the storage(except the > local hard disk), and do not need the block layer at all. > > 1. Is there a way to disable the block layer for specific devices? > > 2. If yes, how can that be done, and are there any gotchas associated with > that?
Mark, Tempting thought that: linux without a block layer. I think you have no hope in the lk 2.4 series and even less in the lk 2.6 series. Now for some thoughts. If you don't need to mount any SCSI disks, you could build a kernel with sd as a module and remove/hide sd_mod.o . A more invasive method would be to modify the sd driver so that it was no longer interested in SCSI devices whose peripheral device type was zero (i.e. disks). On the sg driver side, if lots of sg file descriptors are open to those thousands of SCSI devices, then reducing the per fd SG_DEF_RESERVED_SIZE from 32 KB may help. This could be reduced by editing include/scsi/sg.h . Doug Gilbert - 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
