All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Yongseok Koh <yskoh@mellanox.com>
Subject: [PATCH v2 0/2] net/mlx5: make vectorized Tx threshold configurable
Date: Tue, 30 Oct 2018 07:49:11 +0000	[thread overview]
Message-ID: <20181030074901.40342-1-yskoh@mellanox.com> (raw)
In-Reply-To: <20181029231509.39886-1-yskoh@mellanox.com>

v2:
* add "net/mlx5: move device spawn configuration to probing"
* rename txqs_min_vec to txqs_max_vec

Yongseok Koh (2):
  net/mlx5: move device spawn configuration to probing
  net/mlx5: make vectorized Tx threshold configurable

 doc/guides/nics/mlx5.rst         | 16 ++++++++-
 drivers/net/mlx5/mlx5.c          | 70 ++++++++++++++++++++++++----------------
 drivers/net/mlx5/mlx5.h          |  1 +
 drivers/net/mlx5/mlx5_defs.h     |  6 ++--
 drivers/net/mlx5/mlx5_rxtx_vec.c |  2 +-
 5 files changed, 64 insertions(+), 31 deletions(-)

-- 
2.11.0

  reply	other threads:[~2018-10-30  7:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 23:15 [PATCH] net/mlx5: make vectorized Tx threshold configurable Yongseok Koh
2018-10-30  7:49 ` Yongseok Koh [this message]
2018-10-30  7:49   ` [PATCH v2 1/2] net/mlx5: move device spawn configuration to probing Yongseok Koh
2018-11-01  8:03     ` Shahaf Shuler
2018-10-30  7:49   ` [PATCH v2 2/2] net/mlx5: make vectorized Tx threshold configurable Yongseok Koh
2018-11-01  8:03     ` Shahaf Shuler
2018-11-01 17:20 ` [PATCH v3 0/2] " Yongseok Koh
2018-11-01 17:20   ` [PATCH v3 1/2] net/mlx5: move device spawn configuration to probing Yongseok Koh
2018-11-01 17:20   ` [PATCH v3 2/2] net/mlx5: make vectorized Tx threshold configurable Yongseok Koh
2018-11-04  6:48   ` [PATCH v3 0/2] " 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=20181030074901.40342-1-yskoh@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.