From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH v2 0/3] Fix request completion holes
Date: Thu, 16 Nov 2017 10:58:13 -0500 [thread overview]
Message-ID: <1510847893.8751.0.camel@redhat.com> (raw)
In-Reply-To: <e89f72c6-12ce-c149-c81e-f3adb43a8e9e@grimberg.me>
On Thu, 2017-11-16@17:39 +0200, Sagi Grimberg wrote:
> > Sagi, are you ready for me to take this series in? It seemed like there
> > was a question as to whether you might want to try atomics instead of
> > spin locks, or do you want to stick with spinlocks?
>
> I still need a review for this, and I think we'll get it in through the
> nvme tree (via the block tree). Thanks.
Sorry, I didn't pay that close of attention to the files patched in each
one. I just saw rdma in each subject line and assumed it was an rdma
destined patch series. Looking closer I see it was really just Cc:ed to
linux-rdma for review.
--
Doug Ledford <dledford at redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20171116/3528d82b/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Max Gurtuvoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH v2 0/3] Fix request completion holes
Date: Thu, 16 Nov 2017 10:58:13 -0500 [thread overview]
Message-ID: <1510847893.8751.0.camel@redhat.com> (raw)
In-Reply-To: <e89f72c6-12ce-c149-c81e-f3adb43a8e9e-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On Thu, 2017-11-16 at 17:39 +0200, Sagi Grimberg wrote:
> > Sagi, are you ready for me to take this series in? It seemed like there
> > was a question as to whether you might want to try atomics instead of
> > spin locks, or do you want to stick with spinlocks?
>
> I still need a review for this, and I think we'll get it in through the
> nvme tree (via the block tree). Thanks.
Sorry, I didn't pay that close of attention to the files patched in each
one. I just saw rdma in each subject line and assumed it was an rdma
destined patch series. Looking closer I see it was really just Cc:ed to
linux-rdma for review.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key 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 --]
next prev parent reply other threads:[~2017-11-16 15:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 10:06 [PATCH v2 0/3] Fix request completion holes Sagi Grimberg
2017-11-08 10:06 ` Sagi Grimberg
2017-11-08 10:06 ` [PATCH v2 1/3] nvme-rdma: don't suppress send completions Sagi Grimberg
2017-11-08 10:06 ` Sagi Grimberg
2017-11-09 9:18 ` Christoph Hellwig
2017-11-09 9:18 ` Christoph Hellwig
2017-11-09 11:08 ` Sagi Grimberg
2017-11-09 11:08 ` Sagi Grimberg
2017-11-20 8:18 ` Christoph Hellwig
2017-11-20 8:18 ` Christoph Hellwig
2017-11-20 8:33 ` Sagi Grimberg
2017-11-20 8:33 ` Sagi Grimberg
2017-11-20 9:32 ` Christoph Hellwig
2017-11-20 9:32 ` Christoph Hellwig
2017-11-08 10:06 ` [PATCH v2 2/3] nvme-rdma: don't complete requests before a send work request has completed Sagi Grimberg
2017-11-08 10:06 ` Sagi Grimberg
2017-11-09 9:21 ` Christoph Hellwig
2017-11-09 9:21 ` Christoph Hellwig
2017-11-09 11:14 ` Sagi Grimberg
2017-11-09 11:14 ` Sagi Grimberg
2017-11-20 8:31 ` Christoph Hellwig
2017-11-20 8:31 ` Christoph Hellwig
2017-11-20 8:37 ` Sagi Grimberg
2017-11-20 8:37 ` Sagi Grimberg
2017-11-20 8:41 ` Christoph Hellwig
2017-11-20 8:41 ` Christoph Hellwig
2017-11-20 9:04 ` Sagi Grimberg
2017-11-20 9:04 ` Sagi Grimberg
2017-11-20 9:28 ` Sagi Grimberg
2017-11-20 9:28 ` Sagi Grimberg
2017-11-20 10:49 ` Christoph Hellwig
2017-11-20 10:49 ` Christoph Hellwig
2017-11-20 11:12 ` Sagi Grimberg
2017-11-20 11:12 ` Sagi Grimberg
2017-11-20 11:16 ` Christoph Hellwig
2017-11-20 11:16 ` Christoph Hellwig
2017-11-08 10:06 ` [PATCH v2 3/3] nvme-rdma: wait for local invalidation before completing a request Sagi Grimberg
2017-11-08 10:06 ` Sagi Grimberg
2017-11-09 9:39 ` Christoph Hellwig
2017-11-09 9:39 ` Christoph Hellwig
2017-11-13 22:10 ` [PATCH v2 0/3] Fix request completion holes Doug Ledford
2017-11-13 22:10 ` Doug Ledford
2017-11-16 15:39 ` Sagi Grimberg
2017-11-16 15:39 ` Sagi Grimberg
2017-11-16 15:58 ` Doug Ledford [this message]
2017-11-16 15:58 ` Doug Ledford
2017-11-20 7:37 ` Christoph Hellwig
2017-11-20 7:37 ` Christoph Hellwig
2017-11-20 8:33 ` Sagi Grimberg
2017-11-20 8:33 ` Sagi Grimberg
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=1510847893.8751.0.camel@redhat.com \
--to=dledford@redhat.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.