Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Adit Ranadive <aditr@vmware.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org, pv-drivers@vmware.com
Subject: Re: Re: Re: [PATCH for-rc] RDMA/vmw_pvrdma: Fix the active_speed and phys_state value
Date: Mon, 2 Nov 2020 09:55:25 -0800	[thread overview]
Message-ID: <38f4a89a-c443-2cb2-a3de-89481a86e192@vmware.com> (raw)
In-Reply-To: <e0a834a1-e5ee-4838-4718-d6ded1e954be@vmware.com>

On 10/29/20 9:16 AM, Adit Ranadive wrote:
> On 10/29/20 4:57 AM, Jason Gunthorpe wrote:
>> On Wed, Oct 28, 2020 at 11:19:45PM +0000, Adit Ranadive wrote:
>>> The PVRDMA device still reports the active_speed in u8.
>>> Lets use the ib_eth_get_speed to report the speed and
>>> width. Unfortunately, phys_state gets stored as msb of
>>> the new u16 active_speed.
>>
>> This explanation is not clear, I have no idea what this is fixing
> 
> It seemed more clear to me in my head, I guess :).
> 
> After commit 376ceb31ff87 changed the active_speed attribute to
> u16, both the active_speed and phys_state attributes in the
> pvrdma_port_attr struct are getting stored in this u16. As a 
> result, these show up as invalid values in ibv_devinfo.
> 
> Our device still gives us back a u8 active_speed so both these
> are getting stored in the u16. This fix I proposed simply gets 
> the active_speed from the netdev while the phys_state still 
> needs to come from the pvrdma device, i.e. the msb the of the
> u16. I also removed some unused functions as a result.
> 
> Alternatively, I could change the u8 active_width and u16 
> active_speed to reserved now that we're getting the active_speed
> and active_width from the ib_get_eth_speed function.
> 

Jason, did you have any comments on this or did you want me
to just send v1 with an updated description?

>>
>> Jason
>>

  reply	other threads:[~2020-11-02 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 23:19 [PATCH for-rc] RDMA/vmw_pvrdma: Fix the active_speed and phys_state value Adit Ranadive
2020-10-29 11:57 ` Jason Gunthorpe
2020-10-29 16:16   ` [Suspected Spam] " Adit Ranadive
2020-11-02 17:55     ` Adit Ranadive [this message]
2020-11-02 18:02       ` Jason Gunthorpe
2020-11-02 18:21         ` Adit Ranadive
2020-11-02 18:27           ` Jason Gunthorpe
2020-11-02 18:38             ` [Suspected Spam] " Adit Ranadive
2020-11-02 18:46               ` Jason Gunthorpe
2020-11-03  6:56                 ` Leon Romanovsky
2020-11-03 22:41                   ` Adit Ranadive
2020-11-04  9:50                     ` Leon Romanovsky

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=38f4a89a-c443-2cb2-a3de-89481a86e192@vmware.com \
    --to=aditr@vmware.com \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=pv-drivers@vmware.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