From: Amir Vadai <amirv.mellanox@gmail.com>
To: Shawn Bohrer <shawn.bohrer@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, Amir Vadai <amirv@mellanox.com>
Subject: Re: mlx4 interrupt coalescing not important for small packets?
Date: Sun, 11 Aug 2013 16:23:31 +0300 [thread overview]
Message-ID: <52079053.5070405@gmail.com> (raw)
In-Reply-To: <20130809170637.GA5258@sbohrermbp13-local.rgmadvisors.com>
On 09/08/2013 20:06, Shawn Bohrer wrote:
> I was looking at the adaptive interrupt coalescing algorithm for
> mlx4_en which contains the following snippet:
>
> /* Apply auto-moderation only when packet rate
> * exceeds a rate that it matters */
> if (rate > (MLX4_EN_RX_RATE_THRESH / priv->rx_ring_num) &&
> avg_pkt_size > MLX4_EN_AVG_PKT_SMALL) {
> if (rate < priv->pkt_rate_low)
> moder_time = priv->rx_usecs_low;
> else if (rate > priv->pkt_rate_high)
> moder_time = priv->rx_usecs_high;
> else
> moder_time = (rate - priv->pkt_rate_low) *
> (priv->rx_usecs_high - priv->rx_usecs_low) /
> (priv->pkt_rate_high - priv->pkt_rate_low) +
> priv->rx_usecs_low;
> } else {
> moder_time = priv->rx_usecs_low;
> }
>
> In this case MLX4_EN_AVG_PKT_SMALL is 256 bytes. Can someone explain
> to me why interrupt coalescing is not important for small packets
> regardless of the incoming packet rate?
>
> Thanks,
> Shawn
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
The idea was that for small packets, should enter "latency mode"
regardless the packet rate.
Amir
prev parent reply other threads:[~2013-08-11 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 17:06 mlx4 interrupt coalescing not important for small packets? Shawn Bohrer
2013-08-11 13:23 ` Amir Vadai [this message]
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=52079053.5070405@gmail.com \
--to=amirv.mellanox@gmail.com \
--cc=amirv@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=shawn.bohrer@gmail.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.