From: Manish Chopra <manish.chopra@cavium.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <Yuval.Mintz@cavium.com>,
<rahul.verma@cavium.com>, <sudarsana.kalluru@cavium.com>
Subject: [PATCH v2 net-next 7/7] qed: enhanced per queue max coalesce value.
Date: Wed, 26 Jul 2017 06:07:15 -0700 [thread overview]
Message-ID: <20170726130715.12976-8-manish.chopra@cavium.com> (raw)
In-Reply-To: <20170726130715.12976-1-manish.chopra@cavium.com>
From: Rahul Verma <rahul.verma@cavium.com>
Maximum coalesce per Rx/Tx queue is extended from
255 to 511.
Signed-off-by: Rahul Verma <rahul.verma@cavium.com>
Signed-off-by: Yuval Mintz <yuval.mintz@cavium.com>
---
include/linux/qed/qed_if.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/qed/qed_if.h b/include/linux/qed/qed_if.h
index 2b4720b..cc646ca 100644
--- a/include/linux/qed/qed_if.h
+++ b/include/linux/qed/qed_if.h
@@ -184,7 +184,7 @@ enum qed_led_mode {
#define DIRECT_REG_RD(reg_addr) readl((void __iomem *)(reg_addr))
-#define QED_COALESCE_MAX 0xFF
+#define QED_COALESCE_MAX 0x1FF
#define QED_DEFAULT_RX_USECS 12
#define QED_DEFAULT_TX_USECS 48
--
1.7.1
next prev parent reply other threads:[~2017-07-26 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 13:07 [PATCH v2 net-next 0/7] qed/qede: Enhancements Manish Chopra
2017-07-26 13:07 ` [PATCH v2 net-next 1/7] qede: Add getter APIs support for RX flow classification Manish Chopra
2017-07-26 13:07 ` [PATCH v2 net-next 2/7] qed/qede: Add setter " Manish Chopra
2017-07-26 13:07 ` [PATCH v2 net-next 3/7] qed: Add support for Energy efficient ethernet Manish Chopra
2017-07-26 13:07 ` [PATCH v2 net-next 4/7] qede: Add ethtool " Manish Chopra
2017-07-26 13:07 ` [PATCH v2 net-next 5/7] qed: Add support for vf coalesce configuration Manish Chopra
2017-07-26 13:07 ` [PATCH v2 net-next 6/7] qed: Read per queue coalesce from hardware Manish Chopra
2017-07-26 13:07 ` Manish Chopra [this message]
2017-07-27 7:05 ` [PATCH v2 net-next 0/7] qed/qede: Enhancements 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=20170726130715.12976-8-manish.chopra@cavium.com \
--to=manish.chopra@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rahul.verma@cavium.com \
--cc=sudarsana.kalluru@cavium.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