DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Lilja <ml@napatech.com>
To: "elin.zhang@intel.com" <elin.zhang@intel.com>,
	"jingjing.wu@intel.com" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] drivers/net/i40e/i40e_fdir.c: Improved i40e FDIR programming times
Date: Wed, 26 Apr 2017 11:15:22 +0000	[thread overview]
Message-ID: <b06319b02a2e4cd39c2b791fe7f90d5b@napatech.com> (raw)


During my work (https://www.napatech.com/hw-acceleration-via-rte_flow/)on a flowtable application example that use rte_flow I discovered that the rte_flow programming times on a i40e was +11ms. The patch below result in an average programming time of 22usec with a max of 60usec instead of +11ms.

Could the following patch be useful? There might be a good reason for the original code, I'm unable to tell, so I will let it up to the maintainer to decide.


Signed-off-by: Michael Lilja <ml@napatech.com>
---
drivers/net/i40e/i40e_fdir.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/drivers/net/i40e/i40e_fdir.c b/drivers/net/i40e/i40e_fdir.c
index 28cc554f5..a1ec66063 100644
--- a/drivers/net/i40e/i40e_fdir.c
+++ b/drivers/net/i40e/i40e_fdir.c
@@ -1296,23 +1296,29 @@ i40e_fdir_filter_programming(struct i40e_pf *pf,
     rte_wmb();
     I40E_PCI_REG_WRITE(txq->qtx_tail, txq->tx_tail);
-     for (i = 0; i < I40E_FDIR_WAIT_COUNT; i++) {
-           rte_delay_us(I40E_FDIR_WAIT_INTERVAL_US);
+     for (i = 0; i < (I40E_FDIR_WAIT_COUNT * I40E_FDIR_WAIT_INTERVAL_US); i++) {
           if ((txdp->cmd_type_offset_bsz &
                       rte_cpu_to_le_64(I40E_TXD_QW1_DTYPE_MASK)) ==
                       rte_cpu_to_le_64(I40E_TX_DESC_DTYPE_DESC_DONE))
                 break;
+           rte_delay_us(1);
     }
-     if (i >= I40E_FDIR_WAIT_COUNT) {
+     if (i >= (I40E_FDIR_WAIT_COUNT * I40E_FDIR_WAIT_INTERVAL_US)) {
           PMD_DRV_LOG(ERR, "Failed to program FDIR filter:"
                     " time out to get DD on tx queue.");
           return -ETIMEDOUT;
     }
     /* totally delay 10 ms to check programming status*/
-     rte_delay_us((I40E_FDIR_WAIT_COUNT - i) * I40E_FDIR_WAIT_INTERVAL_US);
+  uint32_t w;
+     for (w = 0; w < (I40E_FDIR_WAIT_COUNT * I40E_FDIR_WAIT_INTERVAL_US); w++) {
+           if (i40e_check_fdir_programming_status(rxq) >= 0) {
+                 break;
+           }
+           rte_delay_us(1);
+     }
     if (i40e_check_fdir_programming_status(rxq) < 0) {
           PMD_DRV_LOG(ERR, "Failed to program FDIR filter:"
-                     " programming status reported.");
+                           " programming status reported.");
           return -ENOSYS;
     }
--
Disclaimer: This email and any files transmitted with it may contain confidential information intended for the addressee(s) only. The information is not to be surrendered or copied to unauthorized persons. If you have received this communication in error, please notify the sender immediately and delete this e-mail from your system.

             reply	other threads:[~2017-04-26 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 11:15 Michael Lilja [this message]
2017-04-28  7:54 ` Wu, Jingjing

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=b06319b02a2e4cd39c2b791fe7f90d5b@napatech.com \
    --to=ml@napatech.com \
    --cc=dev@dpdk.org \
    --cc=elin.zhang@intel.com \
    --cc=jingjing.wu@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).