From: Ophir Munk <ophirmu@mellanox.com>
To: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>,
Ophir Munk <ophirmu@mellanox.com>
Subject: [dpdk-dev] [PATCH v2] fix eBPF handling for non-RSS rules
Date: Mon, 5 Feb 2018 14:40:41 +0000 [thread overview]
Message-ID: <1517841642-10429-1-git-send-email-ophirmu@mellanox.com> (raw)
In-Reply-To: <1517700853-6467-1-git-send-email-ophirmu@mellanox.com>
v2:
* Minor commit message updates
* Update a comment in code
Ophir Munk (1):
net/tap: fix eBPF handling of non-RSS flows
drivers/net/tap/tap_bpf_insns.h | 23 +++++++++++++----------
drivers/net/tap/tap_bpf_program.c | 9 ++++++---
2 files changed, 19 insertions(+), 13 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2018-02-05 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 23:34 [dpdk-dev] [PATCH v1] net/tap: fix eBPF handling of non-RSS flows Ophir Munk
2018-02-05 14:40 ` Ophir Munk [this message]
2018-02-05 14:40 ` [dpdk-dev] [PATCH v2] " Ophir Munk
2018-02-05 14:51 ` Pascal Mazon
2018-02-05 18:10 ` Ferruh Yigit
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=1517841642-10429-1-git-send-email-ophirmu@mellanox.com \
--to=ophirmu@mellanox.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=thomas@monjalon.net \
/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).