> The new ioctl based infrastructure either commits or rollbacks > all objects of the command as one transaction. In order to do > that, we introduce a notion of dealing with a collection of > objects that are related to a specific action. > > This also requires adding a notion of an action and attribute. > An action contains a groups of attributes, where each group > contains several attributes. > > When declaring these actions and attributes, we actually declare > their specifications. When a command is executed, we actually > allocates some space to hold auxiliary information. > > Signed-off-by: Matan Barak <matanb@xxxxxxxxxxxx> > --- Matan, thanks for the RFC! If I got this correctly each object will go through three phases - get, handler, and a put. I don't quite understand how a batch operation, like destroy QPs, can be undone after the handler phase. I do see it working if at first multiple gets are performed and one of them fails. In that case undoing is easy because the handlers weren't invoked yet. In the case were some user-objects failed the operation how is this reflected upwards? Also, I wonder, is there another intention behind batch operations except speed? Thanks, Ram -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
