On Sun, Sep 17, 2017 at 03:56:03PM +0300, Leon Romanovsky wrote: <...> > * uABI Update - Matan Barak And this is the presentation: http://linux-rdma.org/docs/lpc-2017-kabi-matan-barak.pdf > * main purpose: enable it by default > * goals of uABI > * resolve write() security issue > * an extensible approach > * #1 - extensible verbs > * #2 - vendor specific - objects, methods and attributes > * and more: automatic syntatic check, backward compatability, efficiency > * The approach is similar to object oriented programming > * Objects - cq, qp, ... > * Methods- create qp, modify qp, create cq, ... > * Attributes - qp handle, qp type, ... > * Parsing trees types > * Common feature-set - QP, CQ, MW, MR, PD > * specific feature - device, CQ > * driver-specific feature - e.g., MLX object, CQ, QP > * The consolidated driver specific parsing tree will be created from the *supported* common/specific/driver-specific features listed above > * user-space passes an ID that is a 16bit unique number to identify the operation > * Method = name + ID + handler + attributes > * Next > * try the accepted patches yourself. already two verbs are implemented (cq create/destroy) > * transition - > * will need to move *all* verbs to resolve the security issue; will need to recode RDMA CM,... > * But can start transition now to enjoy the extensibility and vendor specific perk > * hopefully we could remove the "experimental" before we transition everything (will take time to convert all..., more than 2 years) > * Red Hat won't take anything in experimental... > * force new features to use the new API? > * choose minimal verb list before removing the 'experimental'? > * compat suggestion: have the old API actually use the new API under the hood > Thanks
Attachment:
signature.asc
Description: PGP signature
