After being able to see the codepath used in 1.8, I modified my
free_thresh and other flags so that Rx Burst Bulk alloc will be used.
This solved the problem (while also increasing performance). I'm not sure why.
This is good enough for me, but I'm willing to keep investigating if
it's of any inte
On Wed, Mar 25, 2015 at 10:22:49AM +0200, Dor Green wrote:
> The printout:
> PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 11, SFP+: 4
> PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x154d
> PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f80c0af0e40
> hw_ring=0x7f811630ce00 dma_addr=0xf1630ce0
The printout:
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 11, SFP+: 4
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x154d
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f80c0af0e40
hw_ring=0x7f811630ce00 dma_addr=0xf1630ce00
PMD: check_rx_burst_bulk_alloc_preconditions(): Rx Burst Bulk Alloc
On Tue, Mar 24, 2015 at 04:10:18PM +0200, Dor Green wrote:
> 1 . The eth_conf is:
>
> static struct rte_eth_conf const ethconf = {
> .link_speed = 0,
> .link_duplex = 0,
>
> .rxmode = {
> .mq_mode = ETH_MQ_RX_RSS,
> .max_rx_pkt_len = ETHER_MAX_LEN,
> .split_hdr
1 . The eth_conf is:
static struct rte_eth_conf const ethconf = {
.link_speed = 0,
.link_duplex = 0,
.rxmode = {
.mq_mode = ETH_MQ_RX_RSS,
.max_rx_pkt_len = ETHER_MAX_LEN,
.split_hdr_size = 0,
.header_split = 0,
.hw_ip_checksum = 0,
.hw_
On Tue, Mar 24, 2015 at 12:54:14PM +0200, Dor Green wrote:
> I've managed to fix it so 1.8 works, and the segmentation fault still occurs.
>
> On Tue, Mar 24, 2015 at 11:55 AM, Dor Green wrote:
> > I tried 1.8, but that fails to initialize my device and fails at the pci
> > probe:
> > "Cause
I've managed to fix it so 1.8 works, and the segmentation fault still occurs.
On Tue, Mar 24, 2015 at 11:55 AM, Dor Green wrote:
> I tried 1.8, but that fails to initialize my device and fails at the pci
> probe:
> "Cause: Requested device :04:00.1 cannot be used"
> Can't even compile 2.
I tried 1.8, but that fails to initialize my device and fails at the pci probe:
"Cause: Requested device :04:00.1 cannot be used"
Can't even compile 2.0rc2 atm, getting:
"/usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:701:1: note:
expected '__m128i' but argument is of type 'int'"
For
I changed it to free and it still happens. Note that the segmentation fault
happens before that anyway.
I am using 1.7.1 at the moment. I can try using a newer version.
On 23 Mar 2015 17:00, "Bruce Richardson" wrote:
> On Mon, Mar 23, 2015 at 04:24:18PM +0200, Dor Green wrote:
> > I'm running a
I'm running a small app which captures packets on a single lcore and
then passes it to other workers for processing.
Before even sending it to processing, when checking some minor
information in the packet mbuf's data I get a segfault.
This code, for example gets a segfault:
struct rte_mbuf *pkt
On Mon, Mar 23, 2015 at 04:24:18PM +0200, Dor Green wrote:
> I'm running a small app which captures packets on a single lcore and
> then passes it to other workers for processing.
>
> Before even sending it to processing, when checking some minor
> information in the packet mbuf's data I get a seg
On Mon, Mar 23, 2015 at 05:19:00PM +0200, Dor Green wrote:
> I changed it to free and it still happens. Note that the segmentation fault
> happens before that anyway.
>
> I am using 1.7.1 at the moment. I can try using a newer version.
I'm using 1.7.X in my open-source DPDK-based app and it works
12 matches
Mail list logo
