From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jacob Keller <jacob.e.keller@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com, Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next v2 10/15] fm10k: introduce ITR_IS_ADAPTIVE macro
Date: Sun, 6 Dec 2015 00:01:29 -0800 [thread overview]
Message-ID: <1449388894-128573-11-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <1449388894-128573-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jacob Keller <jacob.e.keller@intel.com>
Define a macro for identifying when the itr value is dynamic or
adaptive. The concept was taken from i40e. This helps make clear what
the check is, and reduces the line length to something more reasonable
in a few places.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Bruce Allan <bruce.w.allan@intel.com>
Tested-by: Krishneil Singh <krishneil.k.singh@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
drivers/net/ethernet/intel/fm10k/fm10k.h | 2 ++
drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c | 6 ++----
drivers/net/ethernet/intel/fm10k/fm10k_main.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ethernet/intel/fm10k/fm10k.h b/drivers/net/ethernet/intel/fm10k/fm10k.h
index b178905..cea0d94 100644
--- a/drivers/net/ethernet/intel/fm10k/fm10k.h
+++ b/drivers/net/ethernet/intel/fm10k/fm10k.h
@@ -172,6 +172,8 @@ struct fm10k_ring_container {
#define FM10K_ITR_20K 50 /* 50us */
#define FM10K_ITR_ADAPTIVE 0x8000 /* adaptive interrupt moderation flag */
+#define ITR_IS_ADAPTIVE(itr) (!!(itr & FM10K_ITR_ADAPTIVE))
+
#define FM10K_ITR_ENABLE (FM10K_ITR_AUTOMASK | FM10K_ITR_MASK_CLEAR)
static inline struct netdev_queue *txring_txq(const struct fm10k_ring *ring)
diff --git a/drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c b/drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c
index fd29145..a505a50 100644
--- a/drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c
+++ b/drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c
@@ -701,12 +701,10 @@ static int fm10k_get_coalesce(struct net_device *dev,
{
struct fm10k_intfc *interface = netdev_priv(dev);
- ec->use_adaptive_tx_coalesce =
- !!(interface->tx_itr & FM10K_ITR_ADAPTIVE);
+ ec->use_adaptive_tx_coalesce = ITR_IS_ADAPTIVE(interface->tx_itr);
ec->tx_coalesce_usecs = interface->tx_itr & ~FM10K_ITR_ADAPTIVE;
- ec->use_adaptive_rx_coalesce =
- !!(interface->rx_itr & FM10K_ITR_ADAPTIVE);
+ ec->use_adaptive_rx_coalesce = ITR_IS_ADAPTIVE(interface->rx_itr);
ec->rx_coalesce_usecs = interface->rx_itr & ~FM10K_ITR_ADAPTIVE;
return 0;
diff --git a/drivers/net/ethernet/intel/fm10k/fm10k_main.c b/drivers/net/ethernet/intel/fm10k/fm10k_main.c
index 746a198..21d4955 100644
--- a/drivers/net/ethernet/intel/fm10k/fm10k_main.c
+++ b/drivers/net/ethernet/intel/fm10k/fm10k_main.c
@@ -1366,7 +1366,7 @@ static void fm10k_update_itr(struct fm10k_ring_container *ring_container)
unsigned int avg_wire_size, packets;
/* Only update ITR if we are using adaptive setting */
- if (!(ring_container->itr & FM10K_ITR_ADAPTIVE))
+ if (!ITR_IS_ADAPTIVE(ring_container->itr))
goto clear_counts;
packets = ring_container->total_packets;
--
2.5.0
next prev parent reply other threads:[~2015-12-06 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 8:01 [net-next v2 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2015-12-05 Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 01/15] fm10k: set netdev features in one location Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 02/15] fm10k: reset max_queues on init_hw_vf failure Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 03/15] fm10k: always check init_hw for errors Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 04/15] fm10k: reinitialize queuing scheme after calling init_hw Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 05/15] fm10k: Correct typecast in fm10k_update_xc_addr_pf Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 06/15] fm10k: explicitly typecast vlan values to u16 Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 07/15] fm10k: add statistics for actual DWORD count of mbmem mailbox Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 08/15] fm10k: rename mbx_tx_oversized statistic to mbx_tx_dropped Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 09/15] fm10k: Add support for ITR scaling based on PCIe link speed Jeff Kirsher
2015-12-06 8:01 ` Jeff Kirsher [this message]
2015-12-06 8:01 ` [net-next v2 11/15] fm10k: Update adaptive ITR algorithm Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 12/15] fm10k: use macro for default Tx and Rx ITR values Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 13/15] fm10k: change default Tx ITR to 25usec Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 14/15] fm10k: TRIVIAL fix typo of hardware Jeff Kirsher
2015-12-06 8:01 ` [net-next v2 15/15] fm10k: TRIVIAL cleanup order at top of fm10k_xmit_frame Jeff Kirsher
2015-12-06 16:23 ` [net-next v2 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2015-12-05 David Miller
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=1449388894-128573-11-git-send-email-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=jacob.e.keller@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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).