It works fine with DPDK at least.
The problem is that OVDK, especially ovs-dpdk command supported by the
OVDK, doesn't work correctly. I tested the DPDK application, l3fwd, in
order to know where the incorrect operation comes from, either DPDK or OVDK
itself. And I know now the issue seems
I have SUPERMICRO A1SRi-2758F mainboard (onboard Atom C2758),
and onboard NICs work fine with DPDK application.
2014-08-21 18:17 GMT+09:00 BYEONG-GI KIM :
> Well, I did think that the NIC in my testing machine may not support DPDK
> rather than thinking l3fwd is not working.
>
> I just tested
Well, I did think that the NIC in my testing machine may not support DPDK
rather than thinking l3fwd is not working.
I just tested the l3fwd sample application to identify whether the NIC
supports DPDK or not.
Best regards
Byeong-Gi KIM
2014-08-21 18:14 GMT+09:00 Chae-yong Chong :
> Hi
>
>
Hello.
Hmm, the problem is a little complicated. Actually, I'm trying to use
dpdk-ovs with openstack deployment, but it seems not working correctly.
I've thus been trying to keep track of the primary problem of this.
I've thought my machine's hardware requirements may not be satisfied to
support
Hi. I have face a strange error on one of my network cards. Call to
rte_eth_dev_configure returns with error code -22. Increaing the
verbosity level shows the following:
PMD: rte_eth_dev_configure: ethdev port_id=2 nb_rx_queues=3 > 0
EAL: Error - exiting with code: 1
here is the snippet of code
Make ACL library to build/work on 'default' architecture:
- make rte_acl_classify_scalar really scalar
(make sure it wouldn't use sse4 instrincts through resolve_priority()).
- Provide two versions of rte_acl_classify code path:
rte_acl_classify_sse() - could be build and used only on systems
RX and TX Are short hand for Receive and Transmit Queues.
These Queues Store the in/egress packets.
Just looking at the info you've sent it tells you that max_rx_queues
for this dev is 0 (Clearly something is wrong here) so the nb_rx_q
which is 3 is an Invalid Value -EINVAL == -22.
On Thu, Aug
Hello.
I'm now using Intel Atom processor C2758 on the DPDK testing machines, but
it seems not working.
Which sample application would be recommended to test the NIC actually
works well with DPDK?
Best regards
Byeong-Gi KIM
>
> From: BYEONG-GI KIM [mailto:kimbyeonggi at gmail.com]
> Sent: Thursday, August 21, 2014 11:09 AM
> To: Masaru Oki; De Lara Guarch, Pablo; dev at dpdk.org
> Subject: Re: [dpdk-dev] DPDK supported processor
>
> It works fine with DPDK at least.
>
> The problem is that OVDK, especially
Hi,
Documentation and header files describe stat_idx parameter for
rte_eth_dev_set_tx_queue_stats_mapping
and
rte_eth_dev_set_rx_queue_stats_mapping
as
The value must be in the range
[0, RTE_MAX_ETHPORT_QUEUE_STATS_MAPS - 1]
I have not found a definition for RTE_MAX_ETHPORT_QUEUE_STATS_MAPS
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of BYEONG-GI KIM
> Sent: Thursday, August 21, 2014 7:04 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] DPDK supported processor
>
> Hello.
>
> I'm now using Intel Atom processor C2758 on the DPDK testing
Hi all,
Any comments for this patch?
And what's the status for merging it into mainline?
Thanks in advance
Changchun
> -Original Message-
> From: Ouyang, Changchun
> Sent: Friday, August 15, 2014 12:58 PM
> To: dev at dpdk.org
> Cc: Cao, Waterman; Ouyang, Changchun
> Subject: [PATCH]
12 matches
Mail list logo
