From: Bart Van Assche <bvanassche@acm.org>
To: Tal Gilboa <talgi@mellanox.com>,
linux-rdma@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org
Cc: Yamin Friedman <yaminf@mellanox.com>,
Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
Max Gurtovoy <maxg@mellanox.com>,
Idan Burstein <idanb@mellanox.com>,
Tariq Toukan <tariqt@mellanox.com>
Subject: Re: [RFC/PATCH net-next 0/9] net/dim: Support for multiple implementations
Date: Wed, 06 Mar 2019 08:15:21 -0800 [thread overview]
Message-ID: <1551888921.9796.2.camel@acm.org> (raw)
In-Reply-To: <20190306084832.57753-1-talgi@mellanox.com>
On Wed, 2019-03-06 at 10:48 +0200, Tal Gilboa wrote:
> net_dim.h lib exposes an implementation of the DIM algorithm for dynamically-tuned interrupt
> moderation for networking interfaces.
>
> We need the same behavior for any block CQ. The main motivation is two benefit from maximized
> completion rate and reduced interrupt overhead that DIM may provide.
What is a "block CQ"? How does net_dim compare to lib/irq_poll? Which approach
results in the best performance and lowest latency?
Thanks,
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: bvanassche@acm.org (Bart Van Assche)
Subject: [RFC/PATCH net-next 0/9] net/dim: Support for multiple implementations
Date: Wed, 06 Mar 2019 08:15:21 -0800 [thread overview]
Message-ID: <1551888921.9796.2.camel@acm.org> (raw)
In-Reply-To: <20190306084832.57753-1-talgi@mellanox.com>
On Wed, 2019-03-06@10:48 +0200, Tal Gilboa wrote:
> net_dim.h lib exposes an implementation of the DIM algorithm for dynamically-tuned interrupt
> moderation for networking interfaces.
>
> We need the same behavior for any block CQ. The main motivation is two benefit from maximized
> completion rate and reduced interrupt overhead that DIM may provide.
What is a "block CQ"? How does net_dim compare to lib/irq_poll? Which approach
results in the best performance and lowest latency?
Thanks,
Bart.
next prev parent reply other threads:[~2019-03-06 16:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 8:48 [RFC/PATCH net-next 0/9] net/dim: Support for multiple implementations Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 1/9] linux/dim: Move logic to dim.h Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 2/9] linux/dim: Remove "net" prefix from internal DIM members Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 3/9] linux/dim: Rename externally exposed macros Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 4/9] linux/dim: Rename net_dim_sample() to net_dim_create_sample() Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 5/9] linux/dim: Rename externally used net_dim members Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 6/9] linux/dim: Move implementation to .c files Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 7/9] linux/dim: Add completions count to dim_sample Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 8/9] linux/dim: Implement blk_dim.h Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 8:48 ` [RFC/PATCH net-next 9/9] drivers/infiniband: Use blk_dim in infiniband driver Tal Gilboa
2019-03-06 8:48 ` Tal Gilboa
2019-03-06 16:15 ` Bart Van Assche [this message]
2019-03-06 16:15 ` [RFC/PATCH net-next 0/9] net/dim: Support for multiple implementations Bart Van Assche
2019-03-07 1:56 ` Sagi Grimberg
2019-03-07 1:56 ` Sagi Grimberg
2019-03-14 11:45 ` Max Gurtovoy
2019-03-14 11:45 ` Max Gurtovoy
2019-03-14 21:53 ` Sagi Grimberg
2019-03-14 21:53 ` Sagi Grimberg
2019-03-18 9:24 ` Yamin Friedman
2019-03-18 9:24 ` Yamin Friedman
2019-03-18 11:08 ` Max Gurtovoy
2019-03-18 11:08 ` Max Gurtovoy
2019-03-18 15:05 ` Max Gurtovoy
2019-03-18 15:05 ` Max Gurtovoy
2019-03-18 21:34 ` Sagi Grimberg
2019-03-18 21:34 ` Sagi Grimberg
2019-03-20 9:17 ` Max Gurtovoy
2019-03-20 9:17 ` Max Gurtovoy
2019-03-20 11:10 ` Leon Romanovsky
2019-03-20 11:10 ` Leon Romanovsky
2019-03-20 18:34 ` Sagi Grimberg
2019-03-20 18:34 ` Sagi Grimberg
2019-03-24 9:11 ` Leon Romanovsky
2019-03-24 9:11 ` Leon Romanovsky
2019-03-18 21:32 ` Sagi Grimberg
2019-03-18 21:32 ` Sagi Grimberg
2019-03-21 5:53 ` Yamin Friedman
-- strict thread matches above, loose matches on Subject: below --
2019-02-03 13:50 Tal Gilboa
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=1551888921.9796.2.camel@acm.org \
--to=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=idanb@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=talgi@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=yaminf@mellanox.com \
--cc=yishaih@mellanox.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.