On Wed, Aug 21, 2019 at 02:50:16PM +0000, Jason Gunthorpe wrote: > On Wed, Aug 21, 2019 at 05:21:01PM +0300, Yuval Shaia wrote: > > Following patch-set introduce the shared object feature. > > > > A shared object feature allows one process to create HW objects (currently > > PD and MR) so that a second process can import. > > > > Patch-set is logically splits to 4 parts as the following: > > - patches 1 to 7 and 18 are preparation steps. > > - patches 8 to 14 are the implementation of import PD > > - patches 15 to 17 are the implementation of the verb > > - patches 19 to 24 are the implementation of import MR > > This is way too big. 10-14 patches at most in a series. I agree with you. Actually i had an offline discussion with Shamir on that. Shamir view point here is that he wanted to split things to smaller pieces to ease the maintenance (git bisect etc) and code review. So we have two options now, one is to split this patch-set into two separate patch-sets, one will deal with preparation (infrastructure and cleanups) and second with the actual feature. Or second option is to merge some patches, e.x. the patches that installs the hook in providers code could be merged. Not to break Shamir's work i tend to go with the first option. Shamir, what do you think? Yuval > > Jason
