From: Moti Haimovsky <motih@mellanox.com>
To: adrien.mazarguil@6wind.com
Cc: dev@dpdk.org, Moti Haimovsky <motih@mellanox.com>
Subject: [dpdk-dev] [PATCH 1/3] doc: fix remove mlx4 Tx inline compilation option
Date: Thu, 9 Nov 2017 19:30:54 +0200 [thread overview]
Message-ID: <1510248656-194169-2-git-send-email-motih@mellanox.com> (raw)
In-Reply-To: <1510248656-194169-1-git-send-email-motih@mellanox.com>
This patch removes the stale CONFIG_RTE_LIBRTE_MLX4_MAX_INLINE compilation
option from the documentation.
Fixes: 586db080585b ("net/mlx4: remove Tx inline compilation option")
Signed-off-by: Moti Haimovsky <motih@mellanox.com>
---
doc/guides/nics/mlx4.rst | 5 -----
1 file changed, 5 deletions(-)
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index 5c3fb76..be1ba16 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -107,11 +107,6 @@ These options can be modified in the ``.config`` file.
to abort with harmless debugging messages as a workaround.
Relevant only when CONFIG_RTE_LIBRTE_MLX4_DEBUG is enabled.
-- ``CONFIG_RTE_LIBRTE_MLX4_MAX_INLINE`` (default **0**)
-
- Amount of data to be inlined during TX operations. Improves latency but
- lowers throughput.
-
- ``CONFIG_RTE_LIBRTE_MLX4_TX_MP_CACHE`` (default **8**)
Maximum number of cached memory pools (MPs) per TX queue. Each MP from
--
1.8.3.1
next prev parent reply other threads:[~2017-11-09 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 17:30 [dpdk-dev] [PATCH 0/3] doc: documentation update for mlx4 PMD Moti Haimovsky
2017-11-09 17:30 ` Moti Haimovsky [this message]
2017-11-09 17:30 ` [dpdk-dev] [PATCH 2/3] doc: fix mlx4 drop inline receive support Moti Haimovsky
2017-11-09 17:30 ` [dpdk-dev] [PATCH 3/3] doc: update mlx4 documentation Moti Haimovsky
2017-11-09 17:37 ` [dpdk-dev] [PATCH 0/3] doc: documentation update for mlx4 PMD Adrien Mazarguil
2017-11-12 3:46 ` Thomas Monjalon
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=1510248656-194169-2-git-send-email-motih@mellanox.com \
--to=motih@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@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).