From: Bruce Richardson <bruce.richardson@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/6] net/mlx5: performance improvement
Date: Wed, 21 Sep 2016 11:22:21 +0100 [thread overview]
Message-ID: <20160921102221.GD16464@bricha3-MOBL3> (raw)
In-Reply-To: <cover.1474360134.git.nelio.laranjeiro@6wind.com>
On Tue, Sep 20, 2016 at 10:53:45AM +0200, Nelio Laranjeiro wrote:
> - Rework structure elements to reduce their size.
> - Removes a second useless loop in Tx burst function.
>
> This series should be applied on top of "net/mlx5: various fixes".
>
> Changes in v2:
>
> - rework serie to apply it on top of "net/mlx5: various fixes".
>
> Changes in v3:
>
> - Rework some commits log.
>
> Nelio Laranjeiro (6):
> net/mlx5: rework hardware structures
> net/mlx5: reduce memory overhead of Rx/Tx descriptors
> net/mlx5: reduce memory overhead for CQE handling
> net/mlx5: reduce memory overhead for BF handling
> net/mlx5: reduce memory overhead for WQE handling
> net/mlx5: remove gather loop on segments
>
Applied to dpdk-next-net/rel_16_11
/Bruce
next prev parent reply other threads:[~2016-09-21 10:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:09 [dpdk-dev] [PATCH " Nelio Laranjeiro
2016-09-07 7:09 ` [dpdk-dev] [PATCH 1/6] net/mlx5: rework hardware structures Nelio Laranjeiro
2016-09-07 7:09 ` [dpdk-dev] [PATCH 2/6] net/mlx5: reduce Tx and Rx structure size Nelio Laranjeiro
2016-09-07 7:09 ` [dpdk-dev] [PATCH 3/6] " Nelio Laranjeiro
2016-09-07 7:09 ` [dpdk-dev] [PATCH 4/6] net/mlx5: reduce Tx " Nelio Laranjeiro
2016-09-07 7:09 ` [dpdk-dev] [PATCH 5/6] net/mlx5: reduce Tx and Rx " Nelio Laranjeiro
2016-09-07 7:09 ` [dpdk-dev] [PATCH 6/6] net/mlx5: remove gather loop on segments Nelio Laranjeiro
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 0/6] net/mlx5: performance improvement Nelio Laranjeiro
2016-09-19 16:17 ` Bruce Richardson
2016-09-20 7:25 ` Nélio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 " Nelio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 1/6] net/mlx5: rework hardware structures Nelio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 2/6] net/mlx5: reduce memory overhead of Rx/Tx descriptors Nelio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 3/6] net/mlx5: reduce memory overhead for CQE handling Nelio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 4/6] net/mlx5: reduce memory overhead for BF handling Nelio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 5/6] net/mlx5: reduce memory overhead for WQE handling Nelio Laranjeiro
2016-09-20 8:53 ` [dpdk-dev] [PATCH v3 6/6] net/mlx5: remove gather loop on segments Nelio Laranjeiro
2016-09-21 10:22 ` Bruce Richardson [this message]
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 1/6] net/mlx5: rework hardware structures Nelio Laranjeiro
2016-09-19 16:14 ` Bruce Richardson
2016-09-20 7:09 ` Nélio Laranjeiro
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 2/6] net/mlx5: reduce Tx and Rx structure size Nelio Laranjeiro
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 3/6] " Nelio Laranjeiro
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 4/6] net/mlx5: reduce Tx " Nelio Laranjeiro
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 5/6] net/mlx5: reduce Tx and Rx " Nelio Laranjeiro
2016-09-14 12:18 ` [dpdk-dev] [PATCH v2 6/6] net/mlx5: remove gather loop on segments Nelio Laranjeiro
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=20160921102221.GD16464@bricha3-MOBL3 \
--to=bruce.richardson@intel.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).