DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
	Xiaoyun Li <xiaoyun.li@intel.com>
Subject: [dpdk-dev] [RFC] app/testpmd: update to support shared Rx queue
Date: Mon, 2 Aug 2021 13:02:32 +0000	[thread overview]
Message-ID: <DM4PR12MB53738854D62593E4D1A00778A1EF9@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)

To support shared Rx queue[1], plan to update testpmd with following
changes:
- Add ``--rxq-share`` to enable shared Rx queue if device supports.
- In verbose mode, dump mbuf->port for each received packet.
- Check forwarding configuration to make sure queue streams of same
  share group scheduled on same core.
- Change forwarding engines to locate source stream by each packet
  source port, update stream counters and forward according to source
  stream setup.

[1] https://mails.dpdk.org/archives/dev/2021-July/215575.html

Signed-off-by: Xueming Li <xuemingl@nvidia.com>

                 reply	other threads:[~2021-08-02 13:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DM4PR12MB53738854D62593E4D1A00778A1EF9@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=viacheslavo@nvidia.com \
    --cc=xiaoyun.li@intel.com \
    /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).