From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: nelio.laranjeiro@6wind.com, dev@dpdk.org
Subject: Re: [PATCH] net/mlx5: remove excessive data prefetch
Date: Tue, 13 Mar 2018 13:44:59 +0100 [thread overview]
Message-ID: <20180313124459.GI3994@6wind.com> (raw)
In-Reply-To: <20180312170545.16165-1-yskoh@mellanox.com>
On Mon, Mar 12, 2018 at 10:05:45AM -0700, Yongseok Koh wrote:
> In Enhanced Multi-Packet Send (eMPW), entire packet data is prefetched to
> LLC if it isn't inlined. Even though this helps reducing jitter when HW
> fetches data by DMA, this can thresh the LLC with evicting precious data.
> And if the size of queue is large and there are many queues, this might not
> be effective. Also, if application runs on a remote node from the PCIe
> link, it may not be helpful and can even cause bad results.
>
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2018-03-13 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 17:05 [PATCH] net/mlx5: remove excessive data prefetch Yongseok Koh
2018-03-13 12:44 ` Adrien Mazarguil [this message]
2018-04-03 4:58 ` Shahaf Shuler
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=20180313124459.GI3994@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=yskoh@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.