Hi Bean, > > By now we've read the device HPB configuration, and we are ready to > > attach a scsi device to our HPB luns. A perfect timing might be > > while > > scsi is performing its .slave_alloc() or .slave_configure(). > > > > hi, Avri > That means HPB memory allocation done in .scan_finished() ? The specifics of this feature are yet to be determined. Among those, yes - we need to discuss how to handle the memory allocation. Statically allocating the required cache for the entire max-active-subregions, Which may sum-up to a hundreds of MB, has its obvious downsize. We need to discuss this further. > and sd_init_command() needs to change as well, add a new request > type REQ_OP_HPB_READ? Again, this is an implementation issue. We need to figure it out in the sequel. E.g. we might want to make use of the combination of a valid handler and blk_op_is_private. I think it would be more constructive, if we can decide first on the module layout, And figure out the other details as we go? Can you provide the pros and cons for the Samsung approach - implementing all HPB functionalities using a single LLD? Thanks, Avri > > > Bean >
