[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161114.123141.575224690412855747.davem@davemloft.net>
Date: Mon, 14 Nov 2016 12:31:41 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: madalin.bucur@....com
Cc: netdev@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, oss@...error.net,
ppc@...dchasers.com, joe@...ches.com, pebolle@...cali.nl,
joakim.tjernlund@...inera.com
Subject: Re: [PATCH net-next v7 03/10] dpaa_eth: add option to use one
buffer pool set
From: Madalin-Cristian Bucur <madalin.bucur@....com>
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.
Powered by blists - more mailing lists