* [PATCH 0/3] Least attached vector support
@ 2010-05-13 9:25 Yevgeny Petrilin
2013-04-02 14:20 ` Bart Van Assche
0 siblings, 1 reply; 3+ messages in thread
From: Yevgeny Petrilin @ 2010-05-13 9:25 UTC (permalink / raw)
To: Roland Dreier; +Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA
Hello Roland,
Those patches where submitted a while ago, I cleaned them up a little and generated against your latest git.
They allow to hw driver to choose to which EQ a CQ would be attached, considering the load on its eqs.
Thanks,
Yevgeny
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 0/3] Least attached vector support
2010-05-13 9:25 [PATCH 0/3] Least attached vector support Yevgeny Petrilin
@ 2013-04-02 14:20 ` Bart Van Assche
[not found] ` <loom.20130402T161828-251-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Bart Van Assche @ 2013-04-02 14:20 UTC (permalink / raw)
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA
Yevgeny Petrilin <yevgenyp@...> writes:
> Hello Roland,
>
> Those patches where submitted a while ago, I cleaned them up a little and
generated against your latest git.
> They allow to hw driver to choose to which EQ a CQ would be attached,
considering the load on its eqs.
(replying to an e-mail from three years ago)
Hello,
Can anyone tell me what happened with this patch series ? To me this looks like
a useful patch series to make the mlx4_en driver faster. However, I haven't seen
anyone posting any review comments to this series and apparently this
functionality isn't upstream either.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 0/3] Least attached vector support
[not found] ` <loom.20130402T161828-251-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
@ 2013-04-02 17:07 ` Roland Dreier
0 siblings, 0 replies; 3+ messages in thread
From: Roland Dreier @ 2013-04-02 17:07 UTC (permalink / raw)
To: Bart Van Assche; +Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
On Tue, Apr 2, 2013 at 7:20 AM, Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org> wrote:
> Can anyone tell me what happened with this patch series ? To me this looks like
> a useful patch series to make the mlx4_en driver faster. However, I haven't seen
> anyone posting any review comments to this series and apparently this
> functionality isn't upstream either.
It was never clear to me that "number of CQs attached" is a
particularly good way to choose an interrupt vector. It would seem to
me that we would want something that takes into account CPU affinity,
possibly NUMA effects, etc. Also I don't think there were any
performance numbers posted for these changes, were there?
(BTW It would be interesting to know how much improvement one could
get on modern 2/4 socket systems by allocating EQ, CQ, QP, etc. memory
on the "right" NUMA node -- where I don't know if "right" means on the
node closest to the adapter or the node where the CPU will access the
queue)
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-04-02 17:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-13 9:25 [PATCH 0/3] Least attached vector support Yevgeny Petrilin
2013-04-02 14:20 ` Bart Van Assche
[not found] ` <loom.20130402T161828-251-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2013-04-02 17:07 ` Roland Dreier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox