netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] IB/ipoib: move back the IB LL address into the hard header
Date: Tue, 11 Oct 2016 19:37:32 +0200	[thread overview]
Message-ID: <1476207452.448.2.camel@redhat.com> (raw)
In-Reply-To: <20161011173216.GA16892@obsidianresearch.com>

On Tue, 2016-10-11 at 11:32 -0600, Jason Gunthorpe wrote:
> On Tue, Oct 11, 2016 at 07:15:44PM +0200, Paolo Abeni wrote:
> 
> > Also the connected mode maximum mtu is reduced by 16 bytes to
> > cope with the increased hard header len.
> 
> Changing the MTU is going to cause annoying interop problems, can you
> avoid this?

I don't like changing the maximum MTU value, too, but I was unable to
find an alternative solution. The PMTU detection should protect against
such issues. 

  reply	other threads:[~2016-10-11 17:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 17:15 [PATCH] IB/ipoib: move back the IB LL address into the hard header Paolo Abeni
     [not found] ` <1dbd83dfe7f435eecc5bc460e901b47758280f30.1476206016.git.pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-11 17:32   ` Jason Gunthorpe
2016-10-11 17:37     ` Paolo Abeni [this message]
     [not found]       ` <1476207452.448.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-11 17:42         ` Jason Gunthorpe
     [not found]           ` <20161011174224.GA17319-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-11 17:52             ` Paolo Abeni
2016-10-11 17:41     ` Doug Ledford
2016-10-11 18:01       ` Jason Gunthorpe
2016-10-11 18:10         ` Paolo Abeni
     [not found]           ` <1476209407.448.9.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-11 18:17             ` Doug Ledford
     [not found]               ` <073e0007-a43b-134d-ba7e-b290304be585-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-11 18:30                 ` Jason Gunthorpe
     [not found]                   ` <20161011183019.GC20253-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-11 18:50                     ` Doug Ledford
2016-10-12 18:21                       ` Doug Ledford
2016-10-11 18:27             ` Jason Gunthorpe
2016-10-13 14:24   ` David Miller
     [not found]     ` <20161013.102432.1450901395774429343.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-10-13 14:35       ` Doug Ledford
2016-10-13 14:43         ` [PATCH] IB/ipoib: move back the IB LL address into the hard header,Re: " David Miller
     [not found]           ` <20161013.104314.1842951254979604965.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-10-13 15:20             ` Doug Ledford
2016-10-13 15:57               ` [PATCH] IB/ipoib: move back the IB LL address into the hard header,Re: [PATCH] IB/ipoib: move back the IB LL address into the hard header,Re: " David Miller
2016-10-13 15:17     ` Paolo Abeni

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=1476207452.448.2.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=dledford@redhat.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sean.hefty@intel.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).