[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1416966185.29427.46.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Tue, 25 Nov 2014 17:43:05 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: Alexander Duyck <alexander.h.duyck@...hat.com>,
netdev@...r.kernel.org, Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
davem@...emloft.net
Subject: Re: [net-next PATCH 2/5] ethernet/intel: Use eth_skb_pad helper
On Tue, 2014-11-25 at 16:44 -0800, Alexander Duyck wrote:
>
> 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.
Well, many NIC do not have such restriction.
Do we have some kind of counters of skb->head reallocations caused by
this padding ?
I believe I finally have an idea why we had various + 15 in skb
allocations in TCP stack !
We probably should reinstate them, as ACK packets can be 54 bytes long.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists