From: Stephen Hemminger <stephen@networkplumber.org>
To: Ori Kam <orika@mellanox.com>
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
arybchenko@solarflare.com, shahafs@mellanox.com,
viacheslavo@mellanox.com, alexr@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] ethdev: support hairpin queue
Date: Tue, 13 Aug 2019 08:46:19 -0700 [thread overview]
Message-ID: <20190813084619.6b78a7b9@hermes.lan> (raw)
In-Reply-To: <1565703468-55617-1-git-send-email-orika@mellanox.com>
On Tue, 13 Aug 2019 13:37:48 +0000
Ori Kam <orika@mellanox.com> wrote:
> This RFC replaces RFC[1].
>
> The hairpin feature (different name can be forward) acts as "bump on the wire",
> meaning that a packet that is received from the wire can be modified using
> offloaded action and then sent back to the wire without application intervention
> which save CPU cycles.
>
> The hairpin is the inverse function of loopback in which application
> sends a packet then it is received again by the
> application without being sent to the wire.
>
> The hairpin can be used by a number of different NVF, for example load
> balancer, gateway and so on.
>
> As can be seen from the hairpin description, hairpin is basically RX queue
> connected to TX queue.
>
> During the design phase I was thinking of two ways to implement this
> feature the first one is adding a new rte flow action. and the second
> one is create a special kind of queue.
Life would be easier for users if the hairpin was an attribute
of queue configuration, not a separate API call.
next prev parent reply other threads:[~2019-08-13 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 13:37 [dpdk-dev] [RFC] ethdev: support hairpin queue Ori Kam
2019-08-13 15:46 ` Stephen Hemminger [this message]
2019-08-14 5:35 ` Ori Kam
2019-08-14 6:05 ` Ori Kam
2019-08-14 14:56 ` Stephen Hemminger
2019-08-15 4:41 ` Ori Kam
2019-08-25 14:06 ` Ori Kam
2019-09-05 4:00 ` Wu, Jingjing
2019-09-05 5:44 ` Ori Kam
2019-09-06 3:08 ` Wu, Jingjing
2019-09-08 6:44 ` Ori Kam
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=20190813084619.6b78a7b9@hermes.lan \
--to=stephen@networkplumber.org \
--cc=alexr@mellanox.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).