Are you using our e1000 driver and are you using FLEET or TCP/IP when the
problem occurs? Dropping packets on transmit normally occurs when there
are insufficient buffers to hold all the transmit messages. If you can
also post the full output of 'show_pci -v’, that might help.



On 2013/11/12, 5:06 AM, "Armin Steinhoff" <community-noreply@qnx.com>
wrote:

>Hugh,
>
>many thanks ..
>
>I'm testing currently my port of the DPDK from Intel.
>When I send with "testpmd" a burst of packets,  my I210 adapter drops a
>lot of packets.
>
>Do you have an idea why an ethernet adapter is dropping packets when
>packets are transmitted ?
>
>--Armin
>
>
>Hugh Brown wrote:
>> The _CA_PCIÅ  function calls are the same for both PCI and PCIe. The
>>only
>> thing that you won¹t be able to do with these function calls is to
>>access
>> the extended PCIe configuration space, unless the BIOS supports it.
>>
>>
>>
>> On 2013/11/11, 11:39 AM, "Armin Steinhoff" <community-noreply@qnx.com>
>> wrote:
>>
>>> Hi,
>>>
>>> supports QNX 4.25 PCIe interfaces ?
>>>
>>> Regards
>>>
>>> --Armin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> General
>>> http://community.qnx.com/sf/go/post106665
>>> To cancel your subscription to this discussion, please e-mail
>>> general-community-unsubscribe@community.qnx.com
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post106666
>> To cancel your subscription to this discussion, please e-mail
>>general-community-unsubscribe@community.qnx.com
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106683
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com

Hugh,

I'm doing my first tests of a port of the "Data Plan" from Intel:
http://www.youtube.com/watch?v=V6jU0uFa86I
DPDK doesn't use the network infrastructure of QNX.

I will check if there is a buffer issue. Could it be that there are also
flow controls problems with the connected switch port at link layer level ?
The test example "testpmd" blows millions of packets per second.
(testpmd is attached) ....

--Armin


Hugh Brown wrote:
> Are you using our e1000 driver and are you using FLEET or TCP/IP when the
> problem occurs? Dropping packets on transmit normally occurs when there
> are insufficient buffers to hold all the transmit messages. If you can
> also post the full output of 'show_pci -v’, that might help.
>
>
>
> On 2013/11/12, 5:06 AM, "Armin Steinhoff" <community-noreply@qnx.com>
> wrote:
>
>> Hugh,
>>
>> many thanks ..
>>
>> I'm testing currently my port of the DPDK from Intel.
>> When I send with "testpmd" a burst of packets,  my I210 adapter drops a
>> lot of packets.
>>
>> Do you have an idea why an ethernet adapter is dropping packets when
>> packets are transmitted ?
>>
>> --Armin
>>
>>
>> Hugh Brown wrote:
>>> The _CA_PCIÃ…  function calls are the same for both PCI and PCIe. The
>>> only
>>> thing that you won¹t be able to do with these function calls is to
>>> access
>>> the extended PCIe configuration space, unless the BIOS supports it.
>>>
>>>
>>>
>>> On 2013/11/11, 11:39 AM, "Armin Steinhoff" <community-noreply@qnx.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> supports QNX 4.25 PCIe interfaces ?
>>>>
>>>> Regards
>>>>
>>>> --Armin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>>
>>>> General
>>>> http://community.qnx.com/sf/go/post106665
>>>> To cancel your subscription to this discussion, please e-mail
>>>> general-community-unsubscribe@community.qnx.com
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> General
>>> http://community.qnx.com/sf/go/post106666
>>> To cancel your subscription to this discussion, please e-mail
>>> general-community-unsubscribe@community.qnx.com
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post106683
>> To cancel your subscription to this discussion, please e-mail
>> general-community-unsubscribe@community.qnx.com
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post106685
> To cancel your subscription to this discussion, please e-mail general-community-unsubscribe@community.qnx.com

Armin,

Yes, if flow control isn’t properly set, it will also cause lost packets.

Hugh.



On 2013/11/12, 8:48 AM, "Armin Steinhoff" <community-noreply@qnx.com>
wrote:

>
>Hugh,
>
>I'm doing my first tests of a port of the "Data Plan" from Intel:
>http://www.youtube.com/watch?v=V6jU0uFa86I
>DPDK doesn't use the network infrastructure of QNX.
>
>I will check if there is a buffer issue. Could it be that there are also
>flow controls problems with the connected switch port at link layer level
>?
>The test example "testpmd" blows millions of packets per second.
>(testpmd is attached) ....
>
>--Armin
>
>
>Hugh Brown wrote:
>> Are you using our e1000 driver and are you using FLEET or TCP/IP when
>>the
>> problem occurs? Dropping packets on transmit normally occurs when there
>> are insufficient buffers to hold all the transmit messages. If you can
>> also post the full output of 'show_pci -v’, that might help.
>>
>>
>>
>> On 2013/11/12, 5:06 AM, "Armin Steinhoff" <community-noreply@qnx.com>
>> wrote:
>>
>>> Hugh,
>>>
>>> many thanks ..
>>>
>>> I'm testing currently my port of the DPDK from Intel.
>>> When I send with "testpmd" a burst of packets,  my I210 adapter drops a
>>> lot of packets.
>>>
>>> Do you have an idea why an ethernet adapter is dropping packets when
>>> packets are transmitted ?
>>>
>>> --Armin
>>>
>>>
>>> Hugh Brown wrote:
>>>> The _CA_PCIÃ…  function calls are the same for both PCI and PCIe. The
>>>> only
>>>> thing that you won¹t be able to do with these function calls is to
>>>> access
>>>> the extended PCIe configuration space, unless the BIOS supports it.
>>>>
>>>>
>>>>
>>>> On 2013/11/11, 11:39 AM, "Armin Steinhoff" <community-noreply@qnx.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> supports QNX 4.25 PCIe interfaces ?
>>>>>
>>>>> Regards
>>>>>
>>>>> --Armin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>>
>>>>> General
>>>>> http://community.qnx.com/sf/go/post106665
>>>>> To cancel your subscription to this discussion, please e-mail
>>>>> general-community-unsubscribe@community.qnx.com
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>>
>>>> General
>>>> http://community.qnx.com/sf/go/post106666
>>>> To cancel your subscription to this discussion, please e-mail
>>>> general-community-unsubscribe@community.qnx.com
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> General
>>> http://community.qnx.com/sf/go/post106683
>>> To cancel your subscription to this discussion, please e-mail
>>> general-community-unsubscribe@community.qnx.com
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post106685
>> To cancel your subscription to this discussion, please...

After a TON of testing and debugging the issue was that the interface wasn't "up".

So after I loaded the supplicant I just do:

ifconfig tiw_sta0 up

and everything works.

I just wanted to update.

Steve,

I used in my test scenario the original I210 board from Intel.
This board wasn't recognized and wasn't handled by the QNX 6.4.

The test utility "testpmd" sets in general the link up.

Did you disable your board by the network configuration of QNX ?
Are you using QNX6.4 or QNX6.5 ?
There seems to be a conflict in handling of the link status

Thanks a lot for your valuable response!

 Best Regards

--Armin



Steve Iribarne wrote:
> After a TON of testing and debugging the issue was that the interface wasn't "up".
>
> So after I loaded the supplicant I just do:
>
> ifconfig tiw_sta0 up
>
> and everything works.
>
> I just wanted to update.
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post107256
> To cancel your subscription to this discussion, please e-mail general-community-unsubscribe@community.qnx.com
>