ething
wrong for vhost-cuse?
BR
Xu Wen
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: ATT3.txt
URL:
<http://dpdk.org/ml/archives/dev/attachments/20150806/43004fcc/attachment-0001.txt>
Added more extensive documentation for ip_pipeline application.
Signed-off-by: Cristian Dumitrescu
---
doc/guides/index.rst |1 +
doc/guides/ip_pipeline_ug/img/ip_pipelines_1.svg | 718 +
doc/guides/ip_pipeline_ug/img/ip_pipelines_2.svg | 997 +
Hi,
I have created a little testbed for DPDK testing.
NIC: Intel Gigabit 82574L (1-port)
The testbed for DPDK has following structure:
1) al40-118 (10.100.40.118/24): DUT running the DPDK application
2) al40-119 (10.100.40.119/24): Used for sending traffic to al40-118
3) al40-111 (10.100.40.111
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Cristian Dumitrescu
> Sent: Thursday, August 6, 2015 3:48 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: ip_pipeline app user guide
>
> Added more extensive documentation for ip_pipeline application
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Cristian Dumitrescu
> Sent: Thursday, August 6, 2015 2:48 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: ip_pipeline app user guide
>
> Added more extensive documentation for ip_pipeline applicati
Add new known issue where VM power manager app may not work
in a system with more than 64 cores, in release notes.
Signed-off-by: Pablo de Lara
---
doc/guides/rel_notes/known_issues.rst | 24
1 file changed, 24 insertions(+)
diff --git a/doc/guides/rel_notes/known_issue
When using VM power manager app on systems with more than 64 cores,
app could not run even though user does not use cores 64 or higher.
The problem happens only in that case, in which case it will result
in an undefined behaviour.
Thefere, this patch allows the user to run the app on a system with
Pablo de Lara (2):
examples/vm_power_mgr: show warning when using systems with more than
64 cores
doc: add known issue regarding VM power mgr in release notes
doc/guides/rel_notes/known_issues.rst | 24
examples/vm_power_manager/channel_manager.c | 11 +-
Changes include
> Modify rte_eal_vdev_init to return allocated port_id
> Modify rte_eal_probe_one to return allocated port_id
2. Removed following functions
> rte_eth_dev_save and
> rte_eth_dev_get_changed_port
3. Added 2 new functions
> rte_eth_dev_get_port_by_name
> rte_eth_de
Instead of executing following functions before and after vdev_init
> rte_eth_dev_save and
> rte_eth_dev_get_changed_port
update following functions to return allocated port_id.
> rte_eal_vdev_init
> rte_eal_probe_one
Thanks to Tetsuya for his valuable inputs.
Ravi Kerur (1):
Chang
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Monday, August 03, 2015 4:13 PM
> To: Carew, Alan; De Lara Guarch, Pablo
> Cc: dev at dpdk.org; Liu, Yong
> Subject: Re: [dpdk-dev] [PATCH] rte_power: fix sample vm_power_mgr not
> work with Haswell
The patch updates the env_abstraction_layer.rst part in prog_guide.
It adds the RX interrupt event declaration and revises the others in interrupt
event section.
Signed-off-by: Cunming Liang
---
doc/guides/prog_guide/env_abstraction_layer.rst | 34 ++---
1 file changed, 31 i
> -Original Message-
> From: Iremonger, Bernard
> Sent: Wednesday, August 05, 2015 4:04 PM
> To: dev at dpdk.org
> Cc: Jastrzebski, MichalX K; Liu, Yong; Iremonger, Bernard
> Subject: [PATCH v3 1/1] bonding: fix device initialisation error handling
>
> If the name parameter to rte_eth_bond
13 matches
Mail list logo
