> > On Mon, Oct 19, 2015 at 12:43:24PM -0400, ira.weiny@xxxxxxxxx wrote: > > From: Ira Weiny <ira.weiny@xxxxxxxxx> > > > > The following series has bug fixes and updates to the staging hfi1 driver. > > Why are you adding new functionality to this driver before it is moved out of > drivers/staging/ ? I _REALLY_ don't like to see that, because it implies that you > are spending time and energy on new stuff, not fixing up the known issues > instead. Perhaps I did not chose my words carefully enough. The largest issue on the TODO list is the refactoring of the code to be shared between the hfi1 and qib driver. While the hardware between hfi1 and qib is similar and thus the initial code looked similar, our performance tuning on hfi1 has revealed that some changes will be required to the hfi1 code to fully utilize the hardware. We would like to get these updates in to make sure that the refactoring work is done properly for the 2 hardware types. > > Please redo this patch series and don't add new stuff. > I can do this but it will cause us to do our refactoring work 2 times in order for it to be done correctly (properly support both hardware types). Of the 23 patches I sent only one has significant updates which don't conflict with this refactoring work. [PATCH 15/23] staging/rdma/hfi1: Implement Expected Receive TID caching However, without this patch users performance will be impacted. In the interest of full disclosure we still have at least 2 more series, possibly 3 which are similar to this series, bug fixes and performance improvements. Given the above explanation, would you find it acceptable to take these "updates"? I can certainly rework patch 15 to separate out the code clean up as per your other email. Ira _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
