From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH v8 0/7] Automatic affinity settings for nvme-rdma
Date: Fri, 11 Aug 2017 11:42:07 -0400 [thread overview]
Message-ID: <1502466127.3080.41.camel@redhat.com> (raw)
In-Reply-To: <1502219676.3002.11.camel@redhat.com>
On Tue, 2017-08-08@15:14 -0400, Doug Ledford wrote:
> On Thu, 2017-07-13@11:57 +0300, Leon Romanovsky wrote:
> > On Thu, Jul 13, 2017@11:28:22AM +0300, Sagi Grimberg wrote:
> > >
> > > > > Doug, please consider this patch set for inclusion.
> > > >
> > > > On which branch did you base your code?
> > >
> > > Linus 4.12 + block tree updates.
> >
> > Thanks
>
> Hi Sagi,
>
> I've pulled this into a branch and pushed it to my github for 0day
> testing. There were a number of conflicts, so please double check
> that
> my branch is resolved out the way you want. Thanks.
This is now in the official for-next area, thanks.
--
Doug Ledford <dledford at redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
WARNING: multiple messages have this Message-ID (diff)
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Saeed Mahameed
<saeedm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Subject: Re: [PATCH v8 0/7] Automatic affinity settings for nvme-rdma
Date: Fri, 11 Aug 2017 11:42:07 -0400 [thread overview]
Message-ID: <1502466127.3080.41.camel@redhat.com> (raw)
In-Reply-To: <1502219676.3002.11.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, 2017-08-08 at 15:14 -0400, Doug Ledford wrote:
> On Thu, 2017-07-13 at 11:57 +0300, Leon Romanovsky wrote:
> > On Thu, Jul 13, 2017 at 11:28:22AM +0300, Sagi Grimberg wrote:
> > >
> > > > > Doug, please consider this patch set for inclusion.
> > > >
> > > > On which branch did you base your code?
> > >
> > > Linus 4.12 + block tree updates.
> >
> > Thanks
>
> Hi Sagi,
>
> I've pulled this into a branch and pushed it to my github for 0day
> testing. There were a number of conflicts, so please double check
> that
> my branch is resolved out the way you want. Thanks.
This is now in the official for-next area, thanks.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-11 15:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 8:09 [PATCH v8 0/7] Automatic affinity settings for nvme-rdma Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 1/7] mlx5: convert to generic pci_alloc_irq_vectors Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 2/7] mlx5e: don't assume anything on the irq affinity mappings of the device Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 3/7] mlx5: move affinity hints assignments to generic code Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 4/7] RDMA/core: expose affinity mappings per completion vector Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 5/7] mlx5: support ->get_vector_affinity Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 6/7] block: Add rdma affinity based queue mapping helper Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:09 ` [PATCH v8 7/7] nvme-rdma: use intelligent affinity based queue mappings Sagi Grimberg
2017-07-13 8:09 ` Sagi Grimberg
2017-07-13 8:20 ` [PATCH v8 0/7] Automatic affinity settings for nvme-rdma Leon Romanovsky
2017-07-13 8:20 ` Leon Romanovsky
2017-07-13 8:28 ` Sagi Grimberg
2017-07-13 8:28 ` Sagi Grimberg
2017-07-13 8:57 ` Leon Romanovsky
2017-07-13 8:57 ` Leon Romanovsky
2017-08-08 19:14 ` Doug Ledford
2017-08-08 19:14 ` Doug Ledford
2017-08-11 15:42 ` Doug Ledford [this message]
2017-08-11 15:42 ` Doug Ledford
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=1502466127.3080.41.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.