From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH v6 for-4.13 0/7] Automatic affinity settings for nvme over rdma
Date: Fri, 04 Aug 2017 15:18:47 -0400 [thread overview]
Message-ID: <1501874327.79618.12.camel@redhat.com> (raw)
In-Reply-To: <2eecc5bb-e356-73e5-a2fc-1f1867a779f3@grimberg.me>
On Thu, 2017-08-03@18:22 +0300, Sagi Grimberg wrote:
> Doug,
>
> > > > Thanks Sagi,
> > > >
> > > > the whole series looks great to me.
> > > >
> > > > It would be even nicer if the maintainers of the various HCA
> > > > drivers
> > > > could look into adding support..
> > >
> > > Did we make any progress on getting this included?
> >
> > AFAICT, its waiting for Doug to pick it up...
> >
> > Not sure if Saeed is planning to run any tests on this,
> > but its clearly agreed that this is the direction all parties
> > want to take, and we have 6-9 rc's to hash out any issues if
> > exist...
> >
> > > It would be sad to miss another merge window..
> >
> > I hope we don't...
>
> Are you picking this up for 4.14? This already missed two merge
> windows..
You're confusing me Sagi. This thread is the v6 of this patchset.
Don't you have a v8 of this patchset in this mailing list? Are you
saying you want me to grab v6 and not v8, or are you asking in the
wrong thread?
--
Doug Ledford <dledford at redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
next prev parent reply other threads:[~2017-08-04 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 14:37 [PATCH v6 for-4.13 0/7] Automatic affinity settings for nvme over rdma Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 1/7] mlx5: convert to generic pci_alloc_irq_vectors Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 2/7] mlx5e: don't assume anything on the irq affinity mappings of the device Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 3/7] mlx5: move affinity hints assignments to generic code Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 4/7] RDMA/core: expose affinity mappings per completion vector Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 5/7] mlx5: support ->get_vector_affinity Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 6/7] block: Add rdma affinity based queue mapping helper Sagi Grimberg
2017-06-18 14:37 ` [PATCH v6 for-4.13 7/7] nvme-rdma: use intelligent affinity based queue mappings Sagi Grimberg
2017-06-19 12:28 ` [PATCH v6 for-4.13 0/7] Automatic affinity settings for nvme over rdma Christoph Hellwig
2017-06-26 10:01 ` Christoph Hellwig
2017-06-27 7:09 ` Sagi Grimberg
2017-08-03 15:22 ` Sagi Grimberg
2017-08-04 19:18 ` Doug Ledford [this message]
2017-08-07 0:23 ` 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=1501874327.79618.12.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox