* [dpdk-users] Network Drivers
@ 2016-12-27 19:26 Kumaraparameshwaran Rathnavel
0 siblings, 0 replies; 4+ messages in thread
From: Kumaraparameshwaran Rathnavel @ 2016-12-27 19:26 UTC (permalink / raw)
To: users
Hi All,
I find that DPDK provides the Multiqueue support depending on the number of queues in the Hardware. So in case I need an application where I need the order of the packet transmitted or received not to change using multiple queues require the application to maintain the synchronisations. So is the take right from the Mutiqueue point of view.
Thanking You,
Param.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-users] Network Drivers
2016-12-21 22:14 ` Wiles, Keith
@ 2016-12-22 4:14 ` Kumaraparameshwaran Rathnavel
0 siblings, 0 replies; 4+ messages in thread
From: Kumaraparameshwaran Rathnavel @ 2016-12-22 4:14 UTC (permalink / raw)
To: Wiles, Keith; +Cc: users
Sure Keith. Will do that. Thanks for the response.
Thanking You,
Param.
> On 22-Dec-2016, at 3:44 AM, Wiles, Keith <keith.wiles@intel.com> wrote:
>
>
>> On Dec 21, 2016, at 10:46 AM, Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
>>
>> Hi All,
>>
>> When I use the network Drivers provided by the API is the CRC error checking done by the hardware. Or is to be taken care by the software. I do not see any of the example APIs doing . So I just wanted to ask it.
>
> We have a number of checksum the FCS (Frame Checksum) is normally done by the NIC plus FCS errors normally do not transfer the frame into memory. The other Checksums UDP, IP, TCP are done in hardware and software depending on the NIC being used. Need to read the docs for the NIC and then look at the config or setup of the RX/TX for that NIC in the example applications.
>
>>
>> Thanking you,
>> Param
>
> Regards,
> Keith
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-users] Network Drivers
2016-12-21 16:46 Kumaraparameshwaran Rathnavel
@ 2016-12-21 22:14 ` Wiles, Keith
2016-12-22 4:14 ` Kumaraparameshwaran Rathnavel
0 siblings, 1 reply; 4+ messages in thread
From: Wiles, Keith @ 2016-12-21 22:14 UTC (permalink / raw)
To: Kumaraparameshwaran Rathnavel; +Cc: users
> On Dec 21, 2016, at 10:46 AM, Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
>
> Hi All,
>
> When I use the network Drivers provided by the API is the CRC error checking done by the hardware. Or is to be taken care by the software. I do not see any of the example APIs doing . So I just wanted to ask it.
We have a number of checksum the FCS (Frame Checksum) is normally done by the NIC plus FCS errors normally do not transfer the frame into memory. The other Checksums UDP, IP, TCP are done in hardware and software depending on the NIC being used. Need to read the docs for the NIC and then look at the config or setup of the RX/TX for that NIC in the example applications.
>
> Thanking you,
> Param
Regards,
Keith
^ permalink raw reply [flat|nested] 4+ messages in thread
* [dpdk-users] Network Drivers
@ 2016-12-21 16:46 Kumaraparameshwaran Rathnavel
2016-12-21 22:14 ` Wiles, Keith
0 siblings, 1 reply; 4+ messages in thread
From: Kumaraparameshwaran Rathnavel @ 2016-12-21 16:46 UTC (permalink / raw)
To: users
Hi All,
When I use the network Drivers provided by the API is the CRC error checking done by the hardware. Or is to be taken care by the software. I do not see any of the example APIs doing . So I just wanted to ask it.
Thanking you,
Param
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-12-27 19:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-12-27 19:26 [dpdk-users] Network Drivers Kumaraparameshwaran Rathnavel
-- strict thread matches above, loose matches on Subject: below --
2016-12-21 16:46 Kumaraparameshwaran Rathnavel
2016-12-21 22:14 ` Wiles, Keith
2016-12-22 4:14 ` Kumaraparameshwaran Rathnavel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).