All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weihang Li <liweihang@huawei.com>
To: <dledford@redhat.com>, <jgg@ziepe.ca>
Cc: <leon@kernel.org>, <shiraz.saleem@intel.com>, <aditr@vmware.com>,
	<mkalderon@marvell.com>, <aelior@marvell.com>,
	<linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: [PATCH RFC for-next 0/6] ofed support to send ib port link event
Date: Thu, 16 Jan 2020 12:10:41 +0800	[thread overview]
Message-ID: <1579147847-12158-1-git-send-email-liweihang@huawei.com> (raw)

Some provider's driver has supported to send port link event to ofed, but
this function is implemented separately by each manufacturer.

This series provides a solution in ib core, and remove the relevant codes
of some manufacturers, supports reporting port active time during device
registration and sending port error events when device is deregistered.

The key point is how to shield the port event of the backup port in the ib
bonding scenario. Since the active-backup control is judged by the vendor
driver, so the ops.query_port of vendor would determine the port role. And
there is no relevant data structure in ib_core, so modify struct
ib_port_cache to store this information.

Lang Cheng (6):
  RDMA/core: support deliver net device event
  RDMA/mlx5: remove deliver net device event
  RDMA/i40iw: remove deliver net device event
  RDMA/qedr: remove deliver net device event
  RDMA/vmw_pvrdma: remove deliver net device event
  qede: remove invalid notify operation

 drivers/infiniband/core/cache.c                |  21 ++++-
 drivers/infiniband/core/device.c               | 123 +++++++++++++++++++++++++
 drivers/infiniband/hw/i40iw/i40iw_main.c       |   6 --
 drivers/infiniband/hw/i40iw/i40iw_utils.c      |  44 ---------
 drivers/infiniband/hw/mlx5/main.c              |  95 ++-----------------
 drivers/infiniband/hw/qedr/main.c              |  19 ----
 drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c |   5 -
 drivers/net/ethernet/qlogic/qede/qede_rdma.c   |   4 -
 include/rdma/ib_cache.h                        |  13 +++
 include/rdma/ib_verbs.h                        |   8 ++
 10 files changed, 173 insertions(+), 165 deletions(-)

-- 
2.8.1


             reply	other threads:[~2020-01-16  4:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  4:10 Weihang Li [this message]
2020-01-16  4:10 ` [PATCH RFC for-next 1/6] RDMA/core: support deliver net device event Weihang Li
2020-01-16 11:37   ` Leon Romanovsky
2020-01-17 14:23   ` Jason Gunthorpe
     [not found]     ` <19bd56ac-5df5-f5bb-e024-54ef3cd0d0ad@huawei.com>
2020-01-19  9:32       ` Leon Romanovsky
2020-01-16  4:10 ` [PATCH RFC for-next 2/6] RDMA/mlx5: remove " Weihang Li
2020-01-16 11:41   ` Leon Romanovsky
     [not found]     ` <7f3f8190-6b62-f3c6-e4db-2425411fa639@huawei.com>
2020-01-20  7:45       ` Leon Romanovsky
2020-01-16  4:10 ` [PATCH RFC for-next 3/6] RDMA/i40iw: " Weihang Li
2020-01-16  4:10 ` [PATCH RFC for-next 4/6] RDMA/qedr: " Weihang Li
2020-01-16  4:10 ` [PATCH RFC for-next 5/6] RDMA/vmw_pvrdma: " Weihang Li
2020-01-16  4:10 ` [PATCH RFC for-next 6/6] qede: remove invalid notify operation Weihang Li
2020-01-16 11:15 ` [PATCH RFC for-next 0/6] ofed support to send ib port link event 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=1579147847-12158-1-git-send-email-liweihang@huawei.com \
    --to=liweihang@huawei.com \
    --cc=aditr@vmware.com \
    --cc=aelior@marvell.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mkalderon@marvell.com \
    --cc=shiraz.saleem@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 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.