From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-f181.google.com (mail-it1-f181.google.com [209.85.166.181]) by dpdk.org (Postfix) with ESMTP id 4E73D91 for ; Tue, 13 Nov 2018 08:55:49 +0100 (CET) Received: by mail-it1-f181.google.com with SMTP id e11so17082474itl.5 for ; Mon, 12 Nov 2018 23:55:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=McfxyfTTmERI40HZu91knW8vg6EtONCzr6EIOGKLO+Q=; b=Hlf/47rdA3WXYlkrb+JCAEhr5lATWURitccRFubj6q3s0MdULijWkXXjW+hO8KTSjV 63WLu9f1Q7Q0VZy3SOWlEb2VDgvUuVAyJ7vIuqTuuH1oRM7SyNTu1tWWvqeFeMw7XhA1 dGOuOTOlVXDc9yWeWYLb8HIcsZBOVz6CsnmJuq0r674D1K4jMVDMNQLsRIA1cxgNTKiv HOtkXbAYpGRoR+CQW3L08V512xBsLmw8qpUvGjWCyzU85/zW9oqXPEY1v97CnPcMXKGQ 21bLzZhJKw1Zx8XWtkzqQ40Adq6pPSUWcRND+TfU9e0lga/rbIuog9uyC1fpKA0uMj0X U8qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=McfxyfTTmERI40HZu91knW8vg6EtONCzr6EIOGKLO+Q=; b=trbeOz/ZDGX5efI6A0RT8G9ZOu/zL5JBedI6DGyUfO1x/EzYF8E8xIpTpTBJYkh4Du thBRBBv6epLJlrBfdqkaUKvQYpk2uU3jjBu7o+FAmAc4IPmDZoAG/sGTmd9x9RIlAcQh Buxolgx6ObkMWHTBsMR6186mB6sdeAe5koS1s1NJNr8pQrl0woyf1oaA2fAeLtyCd6b/ kytCSr1wj6D/u1ORl82hFjCYBB1VMjUgmeMMUK66crQUNWpGbChe+C0RkgZC66nhv65a J2j5OXsG841SLkcT/QrErk9jnbZD1sqmWHLPZDWFdzHbqyFa5+pCxqxf4eM8IOpel2yQ 2FMA== X-Gm-Message-State: AGRZ1gI7ZBxkhHEd3/lUvZcr5Bq/WiEeC1jBj8QCrqsRqaA+i69TzRca 2h+SKI6wrY0Zgsc0j2EoKmI73o2Br8IWb9Dyrtw= X-Google-Smtp-Source: AJdET5c0SrAgPQFTJN7U9k63/5HGGbZ4eNulhVLVaegiRfNtEVn674jneeYDC/0+K3NqsGy79lUS4NuY12677WJX+pY= X-Received: by 2002:a24:3cd:: with SMTP id e196-v6mr2588119ite.140.1542095748441; Mon, 12 Nov 2018 23:55:48 -0800 (PST) MIME-Version: 1.0 References: <71CBA720-633D-4CFE-805C-606DAAEDD356@intel.com> <3C60E59D-36AD-4382-8CC3-89D4EEB0140D@intel.com> In-Reply-To: From: Harsh Patel Date: Tue, 13 Nov 2018 07:55:37 +0530 Message-ID: To: keith.wiles@intel.com Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Query on handling packets X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2018 07:55:49 -0000 Hello, It would be really helpful if you can provide us a link (for both Tx and Rx) to the project you mentioned earlier where you worked on a similar problem, if possible. Thanks and Regards, Harsh & Hrishikesh. On Mon, 12 Nov 2018 at 01:15, Harsh Patel wrote: > Thanks a lot for all the support. We are looking into our work as of now > and will contact you once we are done checking it completely from our side. > Thanks for the help. > > Regards, > Harsh and Hrishikesh > > On Sat, 10 Nov 2018 at 11:47, Wiles, Keith wrote: > >> Please make sure to send your emails in plain text format. The Mac mail >> program loves to use rich-text format is the original email use it and I >> have told it not only send plain text :-( >> >> > On Nov 9, 2018, at 4:09 AM, Harsh Patel >> wrote: >> > >> > 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? >> > >> >> The PoC code I was developing for DAPI I did not have any performance of >> issues it run just as fast with my limited testing. I converted the l3fwd >> code and I saw 10G 64byte wire rate as I remember using pktgen to generate >> the traffic. >> >> Not sure why you would see a big performance drop, but I do not know your >> application or code. >> >> > Thanks and regards >> > Harsh & Hrishikesh >> > >> > On Thu, 8 Nov 2018 at 23:14, Wiles, Keith >> wrote: >> > >> > >> >> On Nov 8, 2018, at 4:58 PM, Harsh Patel >> 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 >> wrote: >> >> >> >> >> >> > On Nov 8, 2018, at 8:24 AM, Harsh Patel >> 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 >> > >> >> Regards, >> Keith >> >>