DPDK usage discussions
 help / color / mirror / Atom feed
From: Harsh Patel <thadodaharsh10@gmail.com>
To: keith.wiles@intel.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Query on handling packets
Date: Fri, 9 Nov 2018 15:39:19 +0530	[thread overview]
Message-ID: <CAA0iYrFBzO_Bw2bUy46VBjpLJNzos3M57N=nfkx8FNUMgq+2bQ@mail.gmail.com> (raw)
In-Reply-To: <D6A4CD43-BE09-4AFA-A82C-962650011A14@intel.com>

We have implemented the logic for Tx/Rx as you suggested. We compared the
obtained throughput with another version of same application that uses
Linux raw sockets.
Unfortunately, the throughput we receive in our DPDK application is less by
a good margin. Is this any way we can optimize our implementation or
anything that we are missing?

Thanks and regards
Harsh & Hrishikesh

On Thu, 8 Nov 2018 at 23:14, Wiles, Keith <keith.wiles@intel.com> wrote:

>
>
> On Nov 8, 2018, at 4:58 PM, Harsh Patel <thadodaharsh10@gmail.com> wrote:
>
> Thanks for your insight on the topic. Transmission is working with the
> functions you mentioned. We tried to search for some similar functions for
> handling incoming packets but could not find anything. Can you help us on
> that as well?
>
>
> I do not know if a DPDK API set for RX side. But in the DAPI (DPDK API)
> PoC I was working on and presented at the DPDK Summit last Sept. In the PoC
> I did create a RX side version. The issues it has a bit of tangled up in
> the DAPI PoC.
>
> The basic concept is a call to RX a single packet does a rx_burst of N
> number of packets keeping then in a mbuf list. The code would spin waiting
> for mbufs to arrive or return quickly if a flag was set. When it did find
> RX mbufs it would just return the single mbuf and keep the list of mbufs
> for later requests until the list is empty then do another rx_burst call.
>
> Sorry this is a really quick note on how it works. If you need more
> details we can talk more later.
>
>
> Regards,
> Harsh and Hrishikesh.
>
> On Thu, 8 Nov 2018 at 14:26, Wiles, Keith <keith.wiles@intel.com> wrote:
>
>>
>>
>> > On Nov 8, 2018, at 8:24 AM, Harsh Patel <thadodaharsh10@gmail.com>
>> wrote:
>> >
>> > Hi,
>> > We are working on a project where we are trying to integrate DPDK with
>> > another software. We are able to obtain packets from the other
>> environment
>> > to DPDK environment in one-by-one fashion. On the other hand DPDK
>> allows to
>> > send/receive burst of data packets. We want to know if there is any
>> > functionality in DPDK to achieve this conversion of single incoming
>> packet
>> > to a burst of packets sent on NIC and similarly, conversion of burst
>> read
>> > packets from NIC to send it to other environment sequentially?
>>
>>
>> Search in the docs or lib/librte_ethdev directory on
>> rte_eth_tx_buffer_init, rte_eth_tx_buffer, ...
>>
>>
>>
>> > Thanks and regards
>> > Harsh Patel, Hrishikesh Hiraskar
>> > NITK Surathkal
>>
>> Regards,
>> Keith
>>
>>
> Regards,
> Keith
>
>

  reply	other threads:[~2018-11-09 10:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  8:24 Harsh Patel
2018-11-08  8:56 ` Wiles, Keith
2018-11-08 16:58   ` Harsh Patel
2018-11-08 17:43     ` Wiles, Keith
2018-11-09 10:09       ` Harsh Patel [this message]
2018-11-09 21:26         ` Wiles, Keith
2018-11-10  6:17         ` Wiles, Keith
2018-11-11 19:45           ` Harsh Patel
2018-11-13  2:25             ` Harsh Patel
2018-11-13 13:47               ` Wiles, Keith
2018-11-14 13:54                 ` Harsh Patel
2018-11-14 15:02                   ` Wiles, Keith
2018-11-14 15:04                   ` Wiles, Keith
2018-11-14 15:15                   ` Wiles, Keith
2018-11-17 10:22                     ` Harsh Patel
2018-11-17 22:05                       ` Kyle Larose
2018-11-19 13:49                         ` Wiles, Keith
2018-11-22 15:54                           ` Harsh Patel
2018-11-24 15:43                             ` Wiles, Keith
2018-11-24 15:48                               ` Wiles, Keith
2018-11-24 16:01                             ` Wiles, Keith
2018-11-25  4:35                               ` Stephen Hemminger
2018-11-30  9:02                                 ` Harsh Patel
2018-11-30 10:24                                   ` Harsh Patel
2018-11-30 15:54                                   ` Wiles, Keith
2018-12-03  9:37                                     ` Harsh Patel
2018-12-14 17:41                                       ` Harsh Patel
2018-12-14 18:06                                         ` Wiles, Keith
     [not found]                                           ` <CAA0iYrHyLtO3XLXMq-aeVhgJhns0+ErfuhEeDSNDi4cFVBcZmw@mail.gmail.com>
2018-12-30  0:19                                             ` Wiles, Keith
2018-12-30  0:30                                             ` Wiles, Keith
2019-01-03 18:12                                               ` Harsh Patel
2019-01-03 22:43                                                 ` Wiles, Keith
2019-01-04  5:57                                                   ` Harsh Patel
2019-01-16 13:55                                                     ` Harsh Patel
2019-01-30 23:36                                                       ` Harsh Patel
2019-01-31 16:58                                                         ` Wiles, Keith
2019-02-05  6:37                                                           ` Harsh Patel
2019-02-05 13:03                                                             ` Wiles, Keith
2019-02-05 14:00                                                               ` Harsh Patel
2019-02-05 14:12                                                                 ` Wiles, Keith
2019-02-05 14:22                                                                   ` Harsh Patel
2019-02-05 14:27                                                                     ` Wiles, Keith
2019-02-05 14:33                                                                       ` Harsh Patel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA0iYrFBzO_Bw2bUy46VBjpLJNzos3M57N=nfkx8FNUMgq+2bQ@mail.gmail.com' \
    --to=thadodaharsh10@gmail.com \
    --cc=keith.wiles@intel.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).