> >Just still grab the 16 bytes, we don't care about addr3 for passthrough. > >Should be no changes required there. > I was thinking of uring-cmd in general, but then also it does not seem > to collide with xattr. Got your point. > Measure was removing 8b "result" field from passthru-cmd, since 32b CQE > makes that part useless, and we are adding new opcode in nvme > anyway. Maybe we should still reduce passthu-cmd to 64b (rather than 72), > not very sure. Correction above: reduce passthru-cmd to 72b (rather than 80b). -- Joshi
