DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: adrien.mazarguil@6wind.com, nelio.laranjeiro@6wind.com
Cc: dev@dpdk.org, Yongseok Koh <yskoh@mellanox.com>
Subject: [dpdk-dev] [PATCH 0/3] net/mlx5: add Multi-Packet Rx support
Date: Wed,  2 May 2018 16:20:51 -0700	[thread overview]
Message-ID: <20180502232054.7852-1-yskoh@mellanox.com> (raw)

Multi-Packet Rx Queue (MPRQ a.k.a Striding RQ) can further save PCIe
bandwidth by posting a single large buffer for multiple packets. Instead of
posting a buffer per a packet, one large buffer is posted in order to
receive multiple packets on the buffer. A MPRQ buffer consists of multiple
fixed-size strides and each stride receives one packet.

Rx packet is mem-copied to a user-provided mbuf if the size of Rx packet is
comparatively small, or PMD attaches the Rx packet to the mbuf by external
buffer attachment - rte_pktmbuf_attach_extbuf(). A mempool for external
buffers will be allocated and managed by PMD.

This patchset should be applied after:
  net/mlx5: add new Memory Region support

Yongseok Koh (3):
  net/mlx5: separate filling Rx flags
  net/mlx5: add a function to rdma-core glue
  net/mlx5: add Multi-Packet Rx support

 doc/guides/nics/mlx5.rst         |  25 ++
 drivers/net/mlx5/Makefile        |   5 +
 drivers/net/mlx5/mlx5.c          |  66 ++++++
 drivers/net/mlx5/mlx5.h          |   4 +
 drivers/net/mlx5/mlx5_defs.h     |  23 ++
 drivers/net/mlx5/mlx5_ethdev.c   |   3 +
 drivers/net/mlx5/mlx5_glue.c     |  16 ++
 drivers/net/mlx5/mlx5_glue.h     |   8 +
 drivers/net/mlx5/mlx5_prm.h      |  15 ++
 drivers/net/mlx5/mlx5_rxq.c      | 494 ++++++++++++++++++++++++++++++++++++---
 drivers/net/mlx5/mlx5_rxtx.c     | 291 ++++++++++++++++++++---
 drivers/net/mlx5/mlx5_rxtx.h     |  37 ++-
 drivers/net/mlx5/mlx5_rxtx_vec.c |   4 +
 drivers/net/mlx5/mlx5_rxtx_vec.h |   3 +-
 drivers/net/mlx5/mlx5_trigger.c  |   6 +-
 15 files changed, 924 insertions(+), 76 deletions(-)

-- 
2.11.0

             reply	other threads:[~2018-05-02 23:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 23:20 Yongseok Koh [this message]
2018-05-02 23:20 ` [dpdk-dev] [PATCH 1/3] net/mlx5: separate filling Rx flags Yongseok Koh
2018-05-07  5:41   ` Shahaf Shuler
2018-05-02 23:20 ` [dpdk-dev] [PATCH 2/3] net/mlx5: add a function to rdma-core glue Yongseok Koh
2018-05-07  5:46   ` Shahaf Shuler
2018-05-02 23:20 ` [dpdk-dev] [PATCH 3/3] net/mlx5: add Multi-Packet Rx support Yongseok Koh
2018-05-07 10:49   ` Shahaf Shuler
2018-05-09 11:01     ` Yongseok Koh
2018-05-09 11:13 ` [dpdk-dev] [PATCH v2 0/3] " Yongseok Koh
2018-05-09 11:13   ` [dpdk-dev] [PATCH v2 1/3] net/mlx5: separate filling Rx flags Yongseok Koh
2018-05-09 11:13   ` [dpdk-dev] [PATCH v2 2/3] net/mlx5: add a function to rdma-core glue Yongseok Koh
2018-05-09 11:13   ` [dpdk-dev] [PATCH v2 3/3] net/mlx5: add Multi-Packet Rx support Yongseok Koh
2018-05-09 13:57   ` [dpdk-dev] [PATCH v2 0/3] " Shahaf Shuler

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=20180502232054.7852-1-yskoh@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nelio.laranjeiro@6wind.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).