From: <sameehj@amazon.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Sameeh Jubran <sameehj@amazon.com>, <dwmw@amazon.com>,
<zorik@amazon.com>, <matua@amazon.com>, <saeedb@amazon.com>,
<msw@amazon.com>, <aliguori@amazon.com>, <nafea@amazon.com>,
<gtzalik@amazon.com>, <netanel@amazon.com>, <alisaidi@amazon.com>,
<benh@amazon.com>, <akiyano@amazon.com>
Subject: [PATCH V3 net 0/7] Support for dynamic queue size changes
Date: Tue, 11 Jun 2019 14:58:04 +0300 [thread overview]
Message-ID: <20190611115811.2819-1-sameehj@amazon.com> (raw)
From: Sameeh Jubran <sameehj@amazon.com>
This patchset introduces the following:
* add new admin command for supporting different queue size for Tx/Rx
* add support for Tx/Rx queues size modification through ethtool
* allow queues allocation backoff when low on memory
* update driver version
Difference from v2:
* Dropped superfluous range checks which are already done in ethtool. [patch 5/7]
* Dropped inline keyword from function. [patch 4/7]
* Added a new patch which drops inline keyword all *.c files. [patch 6/7]
Difference from v1:
* Changed ena_update_queue_sizes() signature to use u32 instead of int
type for the size arguments. [patch 5/7]
Arthur Kiyanovski (1):
net: ena: add MAX_QUEUES_EXT get feature admin command
Sameeh Jubran (6):
net: ena: enable negotiating larger Rx ring size
net: ena: make ethtool show correct current and max queue sizes
net: ena: allow queue allocation backoff when low on memory
net: ena: add ethtool function for changing io queue sizes
net: ena: remove inline keyword from functions in *.c
net: ena: update driver version from 2.0.3 to 2.1.0
.../net/ethernet/amazon/ena/ena_admin_defs.h | 56 ++-
drivers/net/ethernet/amazon/ena/ena_com.c | 82 +++--
drivers/net/ethernet/amazon/ena/ena_com.h | 3 +
drivers/net/ethernet/amazon/ena/ena_eth_com.c | 26 +-
drivers/net/ethernet/amazon/ena/ena_ethtool.c | 32 +-
drivers/net/ethernet/amazon/ena/ena_netdev.c | 319 +++++++++++++-----
drivers/net/ethernet/amazon/ena/ena_netdev.h | 28 +-
7 files changed, 403 insertions(+), 143 deletions(-)
--
2.17.1
next reply other threads:[~2019-06-11 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 11:58 sameehj [this message]
2019-06-11 11:58 ` [PATCH V3 net 1/7] net: ena: add MAX_QUEUES_EXT get feature admin command sameehj
2019-06-11 11:58 ` [PATCH V3 net 2/7] net: ena: enable negotiating larger Rx ring size sameehj
2019-06-11 11:58 ` [PATCH V3 net 3/7] net: ena: make ethtool show correct current and max queue sizes sameehj
2019-06-11 11:58 ` [PATCH V3 net 4/7] net: ena: allow queue allocation backoff when low on memory sameehj
2019-06-11 11:58 ` [PATCH V3 net 5/7] net: ena: add ethtool function for changing io queue sizes sameehj
2019-06-11 11:58 ` [PATCH V3 net 6/7] net: ena: remove inline keyword from functions in *.c sameehj
2019-06-11 11:58 ` [PATCH V3 net 7/7] net: ena: update driver version from 2.0.3 to 2.1.0 sameehj
2019-06-12 18:22 ` [PATCH V3 net 0/7] Support for dynamic queue size changes 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=20190611115811.2819-1-sameehj@amazon.com \
--to=sameehj@amazon.com \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=gtzalik@amazon.com \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=zorik@amazon.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).