> -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Sunday, August 9, 2015 4:56 PM > To: Jan Kiszka > Cc: dev at dpdk.org; Ouyang, Changchun > Subject: Re: [dpdk-dev] vhost-switch example: huge memory need and CRC > off-loading issue > > 2015-08-08 09:17, Jan Kiszka: > > On 2015-08-08 02:39, Ouyang, Changchun wrote: > > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jan Kiszka > > >> - MAX_QUEUES of 512 causes pretty high memory need for the > application > > >> (something between 1 and 2G) - is that really needed? I'm now running > > >> with 32, and I'm able to get away with 256M. Can we tune this > > >> default? > > > > > > Don't think we need change default just because your platform is 32, > > > Well, my platform is 128, other platform may have other value, :-) > > > > Then let's make it configurable or explore the actual device needs > > before allocating the buffer. The impact on memory consumption is way > > too big to hard-code this, specifically as this is per physical port IIUC. > > You can add a run-time option and/or add a comment in the documentation. > It is just an example, so it must be simple to understand.
Agree, that is better than changing the default macro value.