linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: "Torvalds, Linus" <torvalds@linux-foundation.org>
Cc: "Gunthorpe, Jason" <jgg@ziepe.ca>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PULL REQUEST] Please pull rdma.git
Date: Fri, 21 Jun 2019 15:42:09 -0400	[thread overview]
Message-ID: <3ed43fc8399c5b8efa262699a1d3559cbe41fed5.camel@redhat.com> (raw)

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

Hi Linus,

This is probably our last -rc pull request.  We don't have anything else
outstanding at the moment anyway, and with the summer months on us and
people taking trips, I expect the next weeks leading up to the merge
window to be pretty calm and sedate.

This has two simple, no brainer fixes for the EFA driver.

Then it has ten not quite so simple fixes for the hfi1 driver.  The
problem with them is that they aren't simply one liner typo fixes. 
They're still fixes, but they're more complex issues like livelock under
heavy load where the answer was to change work queue usage and spinlock
usage to resolve the problem, or issues with orphaned requests during
certain types of failures like link down which required some more
complex work to fix too.  They all look like legitimate fixes to me,
they just aren't small like I wish they were.

Here's the boilerplate:

The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:

  Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus

for you to fetch changes up to 7a5834e456f7fb3eca9b63af2a6bc7f460ae482f:

  RDMA/efa: Handle mmap insertions overflow (2019-06-18 16:27:24 -0400)

----------------------------------------------------------------
Pull request for 5.1-rc5

- 2 minor EFA fixes
- 10 hfi1 fixes related to scaling issues

----------------------------------------------------------------
Gal Pressman (2):
      RDMA/efa: Fix success return value in case of error
      RDMA/efa: Handle mmap insertions overflow

Kaike Wan (1):
      IB/hfi1: Validate fault injection opcode user input

Mike Marciniszyn (9):
      IB/hfi1: Close PSM sdma_progress sleep window
      IB/hfi1: Correct tid qp rcd to match verbs context
      IB/hfi1: Avoid hardlockup with flushlist_lock
      IB/hfi1: Silence txreq allocation warnings
      IB/hfi1: Create inline to get extended headers
      IB/hfi1: Use aborts to trigger RC throttling
      IB/hfi1: Wakeup QPs orphaned on wait list after flush
      IB/hfi1: Handle wakeup of orphaned QPs for pio
      IB/hfi1: Handle port down properly in pio

 drivers/infiniband/hw/efa/efa_com_cmd.c  | 24 +++++++++++----
 drivers/infiniband/hw/efa/efa_verbs.c    | 21 ++++++++++---
 drivers/infiniband/hw/hfi1/chip.c        | 13 ++++++++
 drivers/infiniband/hw/hfi1/chip.h        |  1 +
 drivers/infiniband/hw/hfi1/fault.c       |  5 +++
 drivers/infiniband/hw/hfi1/hfi.h         | 31 +++++++++++++++++++
 drivers/infiniband/hw/hfi1/pio.c         | 21 +++++++++++--
 drivers/infiniband/hw/hfi1/rc.c          | 53 +++++++++++++++++++-------------
 drivers/infiniband/hw/hfi1/sdma.c        | 26 ++++++++++++----
 drivers/infiniband/hw/hfi1/tid_rdma.c    |  4 +--
 drivers/infiniband/hw/hfi1/ud.c          |  4 +--
 drivers/infiniband/hw/hfi1/user_sdma.c   | 12 +++-----
 drivers/infiniband/hw/hfi1/user_sdma.h   |  1 -
 drivers/infiniband/hw/hfi1/verbs.c       | 14 +++++----
 drivers/infiniband/hw/hfi1/verbs.h       |  1 +
 drivers/infiniband/hw/hfi1/verbs_txreq.c |  2 +-
 drivers/infiniband/hw/hfi1/verbs_txreq.h |  3 +-
 17 files changed, 174 insertions(+), 62 deletions(-)

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-06-21 19:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 19:42 Doug Ledford [this message]
2019-06-21 22:35 ` [PULL REQUEST] Please pull rdma.git pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-08-30 15:42 Doug Ledford
2019-08-30 16:40 ` pr-tracker-bot
     [not found] <5b0aa103f6007e1887f9b2cacaec8015834589b8.camel@xsintricity.com>
2019-08-23 19:14 ` Doug Ledford
2019-08-14 14:59 Doug Ledford
2019-08-14 18:25 ` pr-tracker-bot
2019-08-19 10:08 ` Geert Uytterhoeven
2019-08-19 12:14   ` Jason Gunthorpe
2019-08-19 12:29     ` Geert Uytterhoeven
2019-08-19 12:48       ` Jason Gunthorpe
2019-08-02 14:39 Doug Ledford
2019-08-02 22:10 ` pr-tracker-bot
2018-12-13 16:56 Doug Ledford
2018-12-13 21:15 ` pr-tracker-bot
     [not found] <58466423-c87e-3921-101e-bffab8989fd8@redhat.com>
     [not found] ` <20161117184950.GP4240@leon.nu>
     [not found]   ` <582E089A.3040106@redhat.com>
     [not found]     ` <20161117200203.GQ4240@leon.nu>
2016-11-17 22:24       ` Or Gerlitz
2016-11-18  2:01         ` Doug Ledford
2016-11-19 19:46           ` Or Gerlitz
2016-11-19 23:11             ` Doug Ledford
2016-11-20 12:53               ` 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=3ed43fc8399c5b8efa262699a1d3559cbe41fed5.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).