> Allow me to ask the question that you asked me before: even though I > didn't see the necessity to set the max budget for zc mode (just > because I didn't spot it happening), would it be better if we separate > both of them because it's an uAPI interface. IIUC, if the setsockopt > is set, we will not separate it any more in the future? > > Or we can keep using the hardcoded value (32) in the zc mode like > before and __only__ touch the copy mode? Then if someone or I found > the significance of making it tunable, then another parameter of > setsockopt can be added? Does it make sense? I found I replied to a wrong thread. Let me copy&paste there instead. Thanks, Jason
