From: Luke Gorrie <luke@snabb.co>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Possible bug in mlx5_tx_burst_mpw?
Date: Fri, 16 Sep 2016 09:57:47 +0200 [thread overview]
Message-ID: <CAA2XHbfVCLL3ERWWKt5iYnAZdzvFwPThDesXx1BSeMXxEG7NxA@mail.gmail.com> (raw)
In-Reply-To: <20160916071403.GW17252@6wind.com>
Hi Adrien,
Thanks for taking the time to write a detailed reply. This indeed sounds
reasonable to me. Users will need to take these special-cases into account
when predicting performance on their own anticipated workloads, which is a
bit tricky, but then that is life when dealing with complex new technology.
I am eager to see what new techniques come down the pipeline for
efficiently moving packets and descriptors across PCIe.
Thanks again for the detailed reply.
Cheers!
-Luke
prev parent reply other threads:[~2016-09-16 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 13:24 Possible bug in mlx5_tx_burst_mpw? Luke Gorrie
2016-09-14 14:30 ` Adrien Mazarguil
2016-09-14 19:33 ` Luke Gorrie
2016-09-16 7:14 ` Adrien Mazarguil
2016-09-16 7:57 ` Luke Gorrie [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=CAA2XHbfVCLL3ERWWKt5iYnAZdzvFwPThDesXx1BSeMXxEG7NxA@mail.gmail.com \
--to=luke@snabb.co \
--cc=dev@dpdk.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 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.