[dpdk-dev] [PATCH] ixgbevf jumbo frame issue with DPDK VF

2014-05-05 Thread Ivan Boule
On 05/01/2014 07:24 PM, Ananyev, Konstantin wrote: > Hi Ivan, > So do I need to split that patch into 2 and resubmit, or can it be applied > like that? Yes, split the patch into 2 independent patches and resubmit them, please. Thanks. Regards, Ivan > Thanks > Konstantin > > -Original

[dpdk-dev] [PATCH 1/7] pci: fix potential mem leak

2014-05-05 Thread David Marchand
Hello Anatoly, Oh yes, missed this one. Ok, I will resubmit an updated patch. Thanks. -- David Marchand On Thu, May 1, 2014 at 5:00 PM, Burakov, Anatoly wrote: > Hi David, > > > Looking at bsd implementation, we can see that there is a potential mem > > leak in linux implementation. Fix

[dpdk-dev] [PATCH RFC] eal: change default per socket memory allocation

2014-05-05 Thread David Marchand
Hello Venky, Anatoly, On Fri, May 2, 2014 at 11:05 AM, Venkatesan, Venky < venky.venkatesan at intel.com> wrote: > Agree with Anatoly - I would much rather not change legacy option > behaviour that has existed for a while, especially when --socket-mem is > available to do exactly what is needed.

[dpdk-dev] [PATCH 5/5] add FILE arguement to debug functions

2014-05-05 Thread Neil Horman
On Sun, May 04, 2014 at 01:17:50PM -0700, Stephen Hemminger wrote: > On Sun, 4 May 2014 08:20:54 -0400 > Neil Horman wrote: > > > On Fri, May 02, 2014 at 04:42:56PM -0700, Stephen Hemminger wrote: > > > The DPDK dump functions are useful for remote debugging of an > > > applications. But when

[dpdk-dev] [PATCH 00/16] [RFC] [VFIO] Add VFIO support to DPDK

2014-05-05 Thread Vincent JARDIN
On 02/05/2014 11:00, Burakov, Anatoly wrote: > Hi Chris, > >> hmm, vfio requires iommu support, however virtio pmd? > > That's correct, virtio will not work with VFIO as it stands. However it's not > the fault of this patch but rather lack of emulated IOMMU on the guest :-) My 2 cents:

[dpdk-dev] [PATCH] eal: parse args before any kinds of init

2014-05-05 Thread Thomas Monjalon
2014-04-15 11:03, Wang Sheng-Hui: > Parse args first, to resolve any invalid args and give out the usage string. > E.g './helloworld --invalid', the '--invalid' will be checked before any > init. After the options are checked, take any init actions. > > Signed-off-by: Wang Sheng-Hui [...] > @@

[dpdk-dev] [PATCH] eal: remove unused fields

2014-05-05 Thread Thomas Monjalon
2014-04-18 09:23, Neil Horman: > On Fri, Apr 18, 2014 at 02:58:08PM +0200, David Marchand wrote: > > There is no need for a 'magic' field in struct rte_config, as this part of > > the structure is local to each process. All threads of a process are > > synchronised because of the run_once atomic.

[dpdk-dev] [PATCH RFC] eal: remove useless output

2014-05-05 Thread Thomas Monjalon
2014-04-30 16:14, David Marchand: > From: Didier Pallard > > Increasing maximum number of lcores gives a huge place to undetected > lcores in output traces. Moreover, this output does not give any > interesting information, since list of undetected lcores can be deduced > from list of detected

[dpdk-dev] [PATCH] eal_lcore.c: print the supported maximum lcores as configured, and detected lcores on eal cpu init

2014-05-05 Thread Thomas Monjalon
2014-04-14 13:37, Wang Sheng-Hui: > Print the maximum lcore(s) as configured, and the number of lcore(s) > detected on eal cpu init as debug info besides the not separate > detected/not-detected lcore info. > > Signed-off-by: Wang Sheng-Hui Added the BSD part, changed title to "eal: print