From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Roland Dreier <roland@purestorage.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Florian Westphal <fw@strlen.de>,
Thadeu Lima de Souza Cascardo <cascardo@redhat.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Resurrecting due to huge ipoib perf regression - [BUG] skb corruption and kernel panic at forwarding with fragmentation
Date: Thu, 7 Jul 2016 17:14:23 -0600 [thread overview]
Message-ID: <20160707231423.GA21039@obsidianresearch.com> (raw)
In-Reply-To: <CAL1RGDVgjRcb23jQQqJ4W-dfm8OkiH6n7hktVLX4mo-oUGj4gA@mail.gmail.com>
On Thu, Jul 07, 2016 at 03:01:40PM -0700, Roland Dreier wrote:
> The reason we moved to the cb storage is that in the past, trying to
> hide some data in the actual skb buffer that we don't actually send
We have neighbour_priv, and ndo_neigh_construct/destruct now ..
A first blush that would seem to be enough to let ipoib store the AH
and other path information in the neigh and avoid the cb? At least the
example in clip sure looks like what ipoib needs to do.
Jason
next prev parent reply other threads:[~2016-07-07 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 6:25 Resurrecting due to huge ipoib perf regression - [BUG] skb corruption and kernel panic at forwarding with fragmentation Roland Dreier
2016-07-07 18:13 ` Alexander Duyck
2016-07-07 22:01 ` Roland Dreier
2016-07-07 22:57 ` Alexander Duyck
2016-07-07 23:14 ` Jason Gunthorpe [this message]
2016-07-08 14:18 ` Roland Dreier
2016-07-08 16:51 ` Jason Gunthorpe
2016-07-08 21:17 ` Roland Dreier
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=20160707231423.GA21039@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=alexander.duyck@gmail.com \
--cc=cascardo@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roland@purestorage.com \
--cc=xiyou.wangcong@gmail.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