From: Govindarajulu Varadarajan <_govind@gmx.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: ssujith@cisco.com, ben@decadent.org.uk,
Govindarajulu Varadarajan <_govind@gmx.com>
Subject: [PATCH net-next v4 0/3] enic: Add support for rx_copybreak
Date: Wed, 3 Sep 2014 03:17:18 +0530 [thread overview]
Message-ID: <1409694441-3843-1-git-send-email-_govind@gmx.com> (raw)
The following series implements rx_copybreak.
dma_map_single()/dma_unmap_single() is more expensive than alloc_skb & memcpy
for smaller packets. By doing this we can reuse the dma buff which is already
mapped. This is very useful when iommu is on. The default skb copybreak value
is 256.
When iommu is on, we can go much higher than 256. All the drivers that supports
rx_copybreak provides module parameter to change this value. Since module
parameter is the least preferred way for changing driver values, this series
adds ethtool support for setting rx_copybreak.
v4:
Validate tunable length in ethtool_get_tunable, not in driver implemented
function.
Loose tunable_ops array for each tunable type. Define one function and let the
driver use switch case for each type.
Use double underscore for data type in UAPI headers.
Use const qualifier where possible.
v3:
Add tunable namespace to ethtool. Use new ethtool cmd ETHTOOL_S/GTUNABLE to
set/get rx_copybreak from userspace.
v2:
Add new ethtool_cmd for DMA buffer parameters, instead of adding new members to
existing ethtool_ringparam.
Govindarajulu Varadarajan (3):
enic: implement rx_copybreak
ethtool: Add generic options for tunables
enic: Add tunable_ops support for rx_copybreak
drivers/net/ethernet/cisco/enic/enic.h | 1 +
drivers/net/ethernet/cisco/enic/enic_ethtool.c | 39 +++++++++++++
drivers/net/ethernet/cisco/enic/enic_main.c | 50 +++++++++++++++-
include/linux/ethtool.h | 4 ++
include/uapi/linux/ethtool.h | 28 +++++++++
net/core/ethtool.c | 81 ++++++++++++++++++++++++++
6 files changed, 200 insertions(+), 3 deletions(-)
--
2.1.0
next reply other threads:[~2014-09-02 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 21:47 Govindarajulu Varadarajan [this message]
2014-09-02 21:47 ` [PATCH net-next v4 1/3] enic: implement rx_copybreak Govindarajulu Varadarajan
2014-09-02 21:47 ` [PATCH net-next v4 2/3] ethtool: Add generic options for tunables Govindarajulu Varadarajan
2014-09-02 21:47 ` [PATCH net-next v4 3/3] enic: Add tunable_ops support for rx_copybreak Govindarajulu Varadarajan
2014-09-05 19:13 ` [PATCH net-next v4 0/3] enic: Add " 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=1409694441-3843-1-git-send-email-_govind@gmx.com \
--to=_govind@gmx.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ssujith@cisco.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).