offload to ssd? neat

I tend to agree with the SSD group. In a $/GB or Watts/GB dogfight, it's hard to justify spending extra die area on something without well understood value. Even if there is a $feature that's a net positive for some use case, where's the 2nd or 3rd source going to come from and will $feature behave the same way across vendors? I think that there are a handful of compute functions that make sense to do within a storage/NVMe controller, but they have to be essentially invisible to applications. Nobody thinks of encryption as a "computational storage" function, but I think it's a good example of a widely deployed compute function in storage devices that makes sense. IMO, DPU-like devices are probably the right place to do any real heavy lifting with storage offloads because their resources/functions are amortized/applied over a number of drives, those drives can come from multiple vendors, and they're not necessarily bound to the block device abstraction.