All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-rc] IB/hfi1: Allow larger MTU without AIP
Date: Tue, 1 Mar 2022 12:59:24 -0400	[thread overview]
Message-ID: <20220301165924.GG6468@ziepe.ca> (raw)
In-Reply-To: <42673e10-e828-fd6c-b098-2638cac6bea9@cornelisnetworks.com>

On Tue, Mar 01, 2022 at 11:49:09AM -0500, Dennis Dalessandro wrote:
> On 2/8/22 2:25 PM, mike.marciniszyn@cornelisnetworks.com wrote:
> > From: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
> > 
> > The AIP code signals the phys_mtu in the following query_port()
> > fragment:
> > 
> > 	props->phys_mtu = HFI1_CAP_IS_KSET(AIP) ? hfi1_max_mtu :
> > 				ib_mtu_enum_to_int(props->max_mtu);
> > 
> > Using the largest MTU possible should not depend on AIP.
> > 
> > Fix by unconditionally using the hfi1_max_mtu value.
> > 
> > Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
> > Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
> >  drivers/infiniband/hw/hfi1/verbs.c | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/drivers/infiniband/hw/hfi1/verbs.c b/drivers/infiniband/hw/hfi1/verbs.c
> > index dc9211f..99d0743 100644
> > +++ b/drivers/infiniband/hw/hfi1/verbs.c
> > @@ -1397,8 +1397,7 @@ static int query_port(struct rvt_dev_info *rdi, u32 port_num,
> >  				      4096 : hfi1_max_mtu), IB_MTU_4096);
> >  	props->active_mtu = !valid_ib_mtu(ppd->ibmtu) ? props->max_mtu :
> >  		mtu_to_enum(ppd->ibmtu, IB_MTU_4096);
> > -	props->phys_mtu = HFI1_CAP_IS_KSET(AIP) ? hfi1_max_mtu :
> > -				ib_mtu_enum_to_int(props->max_mtu);
> > +	props->phys_mtu = hfi1_max_mtu;
> >  
> >  	return 0;
> >  }
> 
> Fixes: 6d72344cf6c4 ("IB/ipoib: Increase ipoib Datagram mode MTU's upper limit")
> 
> Can this just get queued up for-next or should I resubmit with the fixes line above?

Is it OK without the prior patch in the series?

Jason

  reply	other threads:[~2022-03-01 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 19:25 [PATCH for-rc] IB/hfi1: Allow larger MTU without AIP mike.marciniszyn
2022-03-01 16:49 ` Dennis Dalessandro
2022-03-01 16:59   ` Jason Gunthorpe [this message]
2022-03-01 17:06     ` Dennis Dalessandro
2022-03-05  0:24 ` Jason Gunthorpe

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=20220301165924.GG6468@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=linux-rdma@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.