From: Stephen Hemminger <stephen@networkplumber.org>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>,
Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/tap: add RSS hash update callback
Date: Thu, 10 May 2018 09:28:51 -0700 [thread overview]
Message-ID: <20180510092851.1f5a2a5f@xeon-e3> (raw)
In-Reply-To: <1525969418-24504-1-git-send-email-ophirmu@mellanox.com>
On Thu, 10 May 2018 16:23:38 +0000
Ophir Munk <ophirmu@mellanox.com> wrote:
> - * limitation: TAP suppors all of the following hash
> + * limitation: TAP suppors all of IP, UDP and TCP hash
> * functions together and not in partial combinations
s/suppors/supports/
next prev parent reply other threads:[~2018-05-10 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:23 Ophir Munk
2018-05-10 16:28 ` Stephen Hemminger [this message]
2018-05-10 17:25 ` Ophir Munk
2018-05-10 17:30 ` [dpdk-dev] [PATCH v2] " Ophir Munk
2018-05-15 12:21 ` Wiles, Keith
2018-05-17 17:11 ` 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=20180510092851.1f5a2a5f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=shahafs@mellanox.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).