From: Madalin-Cristian Bucur <[email protected]> Date: Mon, 14 Nov 2016 10:25:13 +0000
> I've introduced this Kconfig option as a backwards compatible option, to > be able to run comparative tests between the independent buffer pool setup > and the previous common buffer pool setup. There are not so many reasons > to use the same buffer pool besides "having the old setup", the memory > saving is marginal, in all other aspects the separate buffer pools setup > fares better. > > I'll remove this patch from the next submission. Should anyone care for > this I can add an entry to the feature backlog to add runtime support but > it will be quite low in priority. If it's a debugging feature then that's certainly how this should be handled.
