DPDK usage discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Changchun Zhang <changchun.zhang@oracle.com>,
	"Pathak, Pravin" <pravin.pathak@intel.com>,
	"users@dpdk.org" <users@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] Run-to-completion or Pipe-line for QAT PMD in DPDK
Date: Fri, 18 Jan 2019 16:26:13 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896CD528@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <5e87ae90-94b9-4e85-9172-46b95365ec36@default>

Hi Alex,
> [changchun] In the same thread, but how about to dequeuer at the beginning of the thread each time,
> if data presents then processing them, if no data just do other work, and equeue the packets at some
> time but does not wait.
> For example:
> While(1)
> {
> 	Nb_ops = dequeuer();
> 	If(nb_ops > )
>              {
>                  process_dequeued_data();
>                  continue;
>              }
> 
>               Other_work();
>               If(ipsec)
>                   Enqueuer();
> }
> Does it make sense?
[Fiona] It can, though on the first loop ro after a queit time youll proably get very few back on first and second dequeue as
It'll be called immediately after the enqueue. Once it gets busy that could be ok though

  reply	other threads:[~2019-01-18 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 23:00 Changchun Zhang
2019-01-18 13:13 ` Trahe, Fiona
2019-01-18 14:29   ` Pathak, Pravin
2019-01-18 15:44     ` Changchun Zhang
2019-01-18 16:26       ` Trahe, Fiona [this message]
2019-01-18 16:41         ` Changchun Zhang
2019-01-18 16:57           ` Trahe, Fiona
2019-01-18 17:55             ` Changchun Zhang
2019-01-18 18:20               ` Trahe, Fiona
2019-01-18 18:52                 ` Changchun Zhang

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=348A99DA5F5B7549AA880327E580B435896CD528@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=changchun.zhang@oracle.com \
    --cc=pravin.pathak@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).