From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Vasily Philipov <vasilyf@mellanox.com>, dev@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/mlx4: get back RX flow functionality
Date: Mon, 25 Sep 2017 14:42:39 +0100 [thread overview]
Message-ID: <23328a08-13d1-9483-c6d6-db619ad78eae@intel.com> (raw)
In-Reply-To: <fa8e5827c13923dd42fa54405c9b1069adcf718a.1501749963.git.vasilyf@mellanox.com>
On 8/3/2017 9:49 AM, Vasily Philipov wrote:
> Getting hw directly on RX fast path without verbs call.
>
> Now the number of scatters is calculating on the fly, according to the
> maximum expected packet size.
>
> Signed-off-by: Vasily Philipov <vasilyf@mellanox.com>
I will update series as superseded with [1], please shout if this is wrong.
Thanks,
ferruh
[1]
http://dpdk.org/dev/patchwork/patch/27881/
Moti's mlx4 patchset with 5 patches.
prev parent reply other threads:[~2017-09-25 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 8:49 Vasily Philipov
2017-08-03 8:49 ` [dpdk-dev] [PATCH 2/2] net/mlx4: get back RX offloads Vasily Philipov
2017-09-25 13:42 ` Ferruh Yigit [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=23328a08-13d1-9483-c6d6-db619ad78eae@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=vasilyf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).