Hi Thomas, > Having --socket-mem option to explicitly configure NUMA is OK. > Having -m option for simple configuration is OK.
Exactly. No explicit requirements - use -m option. Explicit socket requirements - use --socket-mem option. > So I don't understand why we shouldn't do this enhancement. I don't know if > "overcomplication" is a good argument. I don't see any reasons *for* this change. IMO this patch tries to fix a problem that doesn't exist (or, rather, a problem that is already solved with --socket-mem switch). I'm open to persuasion on that one of course, but so far I don't see any compelling reason to change -m switch to be more like --socket-mem switch when we already have the --socket-mem switch for cases when the user cares about where the memory comes from. Best regards, Anatoly Burakov DPDK SW Engineer
