Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet-rdma: Fix missing dma sync to nvme data structures
Date: Sat, 14 Jan 2017 17:18:00 +0100	[thread overview]
Message-ID: <20170114161800.GA635@lst.de> (raw)
In-Reply-To: <45c8815c-d9a1-4a74-8a70-0a0ea11d8201@grimberg.me>

On Fri, Jan 13, 2017@10:01:23PM +0200, Sagi Grimberg wrote:
> I've been seeing reports that nvme-rdma is not
> useable with rxe as it crashes pretty consistently.
>
> In any event, we can either add this with 'ib_' prefix
> into 4.10-rc and add a patch to Bart's series or
> we can send a dedicated patch for stable.
>
> Christoph, whats your preference?

Get the ib_dma_* version of Parave's patch in for 4.10-rc.

  parent reply	other threads:[~2017-01-14 16:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 22:45 [PATCH] nvmet-rdma: Fix missing dma sync to nvme data structures Parav Pandit
2017-01-13  7:44 ` Christoph Hellwig
2017-01-13 15:08   ` Parav Pandit
2017-01-13 19:42     ` Sagi Grimberg
2017-01-13 19:50       ` Parav Pandit
2017-01-13 20:01         ` Sagi Grimberg
2017-01-14 16:12           ` Parav Pandit
2017-01-14 21:00             ` Sagi Grimberg
2017-01-14 16:18           ` Christoph Hellwig [this message]
2017-01-14 21:04             ` Sagi Grimberg
2017-01-13 19:35   ` Sagi Grimberg
  -- strict thread matches above, loose matches on Subject: below --
2017-01-14 16:45 Parav Pandit
2017-01-14 21:07 ` Sagi Grimberg
2017-01-16 15:31 ` Christoph Hellwig
2017-01-16 17:18   ` Parav Pandit
2017-01-16 17:30     ` Christoph Hellwig
2017-01-12 22:42 Parav Pandit
2017-01-12 22:45 ` Parav Pandit

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=20170114161800.GA635@lst.de \
    --to=hch@lst.de \
    /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