[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1410359072.7106.27.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 10 Sep 2014 07:24:32 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Or Gerlitz <ogerlitz@...lanox.com>
Cc: Chuck Lever <chuck.lever@...cle.com>,
Govindarajulu Varadarajan <_govind@....com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
LKML Kernel <linux-kernel@...r.kernel.org>,
linux-rdma <linux-rdma@...r.kernel.org>,
Bart Van Assche <bvanassche@....org>,
Saeed Mahameed <saeedm@...lanox.com>,
Tal Alon <talal@...lanox.com>,
Yevgeny Petrilin <yevgenyp@...lanox.com>,
Roland Dreier <roland@...nel.org>
Subject: Re: 3.17-rc1 oops during network interface configuration
On Wed, 2014-09-10 at 10:42 +0300, Or Gerlitz wrote:
> Hi Chuck, thanks for bisecting this out. Indeed, as of this kernel 3.2
> commit 936d7de "IPoIB: Stop lying about hard_header_len and use skb->cb
> to stash LL addresses" we are using the skb->cb field to enable proper
> work under GRO and avoid another historical quirk we had there... so I
> think we can definetly consider commit e0f31d849 to introduce a severe
> regression... Govindarajulu, Dave - what's your thinking here? any quick
> idea on how to fix?
I mentioned the IB stuff when patch was posted, and David replied :
"I think this is fine, IPOIB's control block will need still just 44
bytes after these changes, so there will still be 4 bytes to spare."
http://patchwork.ozlabs.org/patch/357584/
My suggestion was to reduce sch_choke usage and not store the whole
flow_keys.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists