public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Erez Shitrit <erezsh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next] IB/IPoIB: Forward MTU change to driver below
Date: Tue, 23 May 2017 12:24:28 +0300	[thread overview]
Message-ID: <20170523092428.GK17751@mtr-leonro.local> (raw)
In-Reply-To: <20170523085645.GA5877@yuval-lap>

[-- Attachment #1: Type: text/plain, Size: 2611 bytes --]

On Tue, May 23, 2017 at 11:56:45AM +0300, Yuval Shaia wrote:
> On Tue, May 23, 2017 at 11:42:52AM +0300, Leon Romanovsky wrote:
> > From: Erez Shitrit <erezsh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> >
> > This patch checks if there is a driver below that
>
> Is it "below" or "upper" in the driver hierarchy?

The part which  close to the HW. I called it "below".

>
> > needs to be updated on the new MTU and calls it
> > accordingly.
> >
> > Signed-off-by: Erez Shitrit <erezsh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> > Reviewed by: Alex Vesker <valex-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> > Signed-off-by: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> > ---
> >  drivers/infiniband/ulp/ipoib/ipoib_main.c | 19 +++++++++++++++++--
> >  1 file changed, 17 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_main.c b/drivers/infiniband/ulp/ipoib/ipoib_main.c
> > index 2869d1adb1de..28068140800c 100644
> > --- a/drivers/infiniband/ulp/ipoib/ipoib_main.c
> > +++ b/drivers/infiniband/ulp/ipoib/ipoib_main.c
> > @@ -233,6 +233,7 @@ static netdev_features_t ipoib_fix_features(struct net_device *dev, netdev_featu
> >  static int ipoib_change_mtu(struct net_device *dev, int new_mtu)
> >  {
> >  	struct ipoib_dev_priv *priv = ipoib_priv(dev);
> > +	int ret = 0;
> >
> >  	/* dev->mtu > 2K ==> connected mode */
> >  	if (ipoib_cm_admin_enabled(dev)) {
> > @@ -256,9 +257,23 @@ static int ipoib_change_mtu(struct net_device *dev, int new_mtu)
> >  		ipoib_dbg(priv, "MTU must be smaller than the underlying "
> >  				"link layer MTU - 4 (%u)\n", priv->mcast_mtu);
> >
> > -	dev->mtu = min(priv->mcast_mtu, priv->admin_mtu);
> > +	new_mtu = min(priv->mcast_mtu, priv->admin_mtu);
> >
> > -	return 0;
> > +	if (priv->rn_ops->ndo_change_mtu) {
> > +		bool carrier_status = netif_carrier_ok(dev);
> > +
> > +		netif_carrier_off(dev);
> > +
> > +		/* notify lower level on the real mtu */
> > +		ret = priv->rn_ops->ndo_change_mtu(dev, new_mtu);
> > +
> > +		if (carrier_status)
> > +			netif_carrier_on(dev);
> > +	} else {
> > +		dev->mtu = new_mtu;
> > +	}
>
> So we don't want dev->mtu to be updated if driver was registered?

It is updated in ndo_change_mtu call. See nes. cxgb3/4 and mlx4/5 as an
example.

>
> > +
> > +	return ret;
> >  }
> >
> >  /* Called with an RCU read lock taken */
> > --
> > 2.12.2
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-05-23  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  8:42 [PATCH rdma-next] IB/IPoIB: Forward MTU change to driver below Leon Romanovsky
     [not found] ` <20170523084252.16018-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-05-23  8:56   ` Yuval Shaia
2017-05-23  9:24     ` Leon Romanovsky [this message]
     [not found]       ` <20170523092428.GK17751-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-05-23 11:13         ` Yuval Shaia
2017-07-22 17:07   ` Doug Ledford

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=20170523092428.GK17751@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=erezsh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.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