From: Alexander Duyck <alexander.duyck@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: netdev@vger.kernel.org,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
davem@davemloft.net
Subject: Re: [net-next PATCH 2/5] ethernet/intel: Use eth_skb_pad helper
Date: Tue, 25 Nov 2014 16:44:19 -0800 [thread overview]
Message-ID: <54752263.2040204@gmail.com> (raw)
In-Reply-To: <1416957251.29427.39.camel@edumazet-glaptop2.roam.corp.google.com>
On 11/25/2014 03:14 PM, Eric Dumazet wrote:
> On Tue, 2014-11-25 at 14:44 -0800, Alexander Duyck wrote:
>> Update the Intel Ethernet drivers to use eth_skb_pad() instead of doing
>> their own implementations of the function.
>>
>> Also this cleans up two other spots where skb_pad was called but the length
>> and tail pointers were being manipulated directly instead of just having
>> the padding length added via __skb_put.
>>
>> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> Signed-off-by: Alexander Duyck <alexander.h.duyck@redhat.com>
>> ---
>> drivers/net/ethernet/intel/e1000/e1000_main.c | 8 ++------
>> drivers/net/ethernet/intel/fm10k/fm10k_main.c | 11 +++--------
>> drivers/net/ethernet/intel/igb/igb_main.c | 11 +++--------
>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 11 +++--------
>> drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 11 +++--------
>> 5 files changed, 14 insertions(+), 38 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
>> index 24f3986..862d198 100644
>> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
>> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
>> @@ -3136,12 +3136,8 @@ static netdev_tx_t e1000_xmit_frame(struct sk_buff *skb,
>> * packets may get corrupted during padding by HW.
>> * To WA this issue, pad all small packets manually.
>> */
>> - if (skb->len < ETH_ZLEN) {
>> - if (skb_pad(skb, ETH_ZLEN - skb->len))
>> - return NETDEV_TX_OK;
>> - skb->len = ETH_ZLEN;
>> - skb_set_tail_pointer(skb, ETH_ZLEN);
>> - }
>> + if (eth_skb_pad(skb))
>> + return NETDEV_TX_OK;
>>
> Its a bit sad almost no driver increments some drop counter.
>
> This probably could be generically done in eth_skb_pad()
>
> atomic_long_inc(&skb->dev->tx_dropped)
The only problem is eth_skb_pad is called in the Rx path of some drivers
as well.
I wonder if we couldn't make this some sort of netdevice attribute to
indicate what the smallest frame we can handle is and then just pad the
frame to that as a part of __dev_xmit_skb. Then we could do that
outside of the locks and take care of it before we even hit the qdisc layer.
- Alex
next prev parent reply other threads:[~2014-11-26 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 22:43 [net-next PATCH 0/5] net: Add helper for padding short Ethernet frames Alexander Duyck
2014-11-25 22:44 ` [net-next PATCH 1/5] etherdevice: Add function for handling padding frame to ETH_ZLEN Alexander Duyck
2014-11-26 0:56 ` Florian Fainelli
2014-11-26 2:44 ` Alexander Duyck
2014-11-25 22:44 ` [net-next PATCH 2/5] ethernet/intel: Use eth_skb_pad helper Alexander Duyck
2014-11-25 23:14 ` Eric Dumazet
2014-11-26 0:44 ` Alexander Duyck [this message]
2014-11-26 1:05 ` Florian Fainelli
2014-11-26 1:43 ` Eric Dumazet
2014-11-26 3:19 ` David Miller
2014-11-26 4:01 ` Eric Dumazet
2014-11-26 20:41 ` David Miller
2014-11-25 22:44 ` [net-next PATCH 3/5] niu: " Alexander Duyck
2014-11-25 22:44 ` [net-next PATCH 4/5] myri10ge: use " Alexander Duyck
2014-11-25 22:44 ` [net-next PATCH 5/5] r8169: Use eth_skb_pad function Alexander Duyck
2014-11-26 0:02 ` Francois Romieu
2014-11-26 0:33 ` Alexander Duyck
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=54752263.2040204@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
/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).