From: Bart Van Assche <Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: "liranl-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
<liranl-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"ofvwg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
<ofvwg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ANNOUNCE] Open Fabrics Verbs Working Group (OFVWG) meeting next week - 2/7/2017 at 11:00PST
Date: Thu, 2 Feb 2017 22:24:16 +0000 [thread overview]
Message-ID: <1486074223.2816.16.camel@sandisk.com> (raw)
In-Reply-To: <HE1PR0501MB2812A57B3A481B29DE090E2AB14C0-692Kmc8YnlIVrnpjwTCbp8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
On Thu, 2017-02-02 at 22:17 +0000, Liran Liss wrote:
> We would like to solicit a discussion next week on an API proposal
> for binding RDMA completion vectors to CPUs.
Hello Liran,
Are you aware that Christoph Hellwig's patch series for automatically
spreading IRQs over CPUs has been accepted upstream some time ago? See
also pci_alloc_irq_vectors_affinity() in drivers/pci/msi.c. Is the scope
of this meeting to modify that existing functionality or are you perhaps
looking for an API that allows to query the mapping chosen by
pci_alloc_irq_vectors_affinity()?
Thanks,
Bart.--
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-02-02 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 22:17 [ANNOUNCE] Open Fabrics Verbs Working Group (OFVWG) meeting next week - 2/7/2017 at 11:00PST Liran Liss
[not found] ` <HE1PR0501MB2812A57B3A481B29DE090E2AB14C0-692Kmc8YnlIVrnpjwTCbp8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-02-02 22:24 ` Bart Van Assche [this message]
[not found] ` <1486074223.2816.16.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-02-06 20:05 ` Liran Liss
2017-02-03 7:42 ` Christoph Hellwig
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=1486074223.2816.16.camel@sandisk.com \
--to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liranl-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=ofvwg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.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