From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Pascal Mazon <pascal.mazon@6wind.com>,
motih@mellanox.com, ophirmu@mellanox.com
Cc: dev@dpdk.org, Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/tap: remove queue specific offload support
Date: Thu, 12 Apr 2018 17:23:45 +0100 [thread overview]
Message-ID: <e2cea389-14ac-2aeb-0426-d20b692e2ebe@intel.com> (raw)
In-Reply-To: <2913888.DGWfva7bOG@xps>
On 4/5/2018 6:49 PM, Thomas Monjalon wrote:
> Pascal, Moti, Ophir,
> please comment.
Hi Moti,
Any comment? This has been asked many times now.
>
> 22/03/2018 19:28, Ferruh Yigit:
>> It is not clear if tap PMD supports queue specific offloads, removing
>> the related code.
>>
>> Fixes: 95ae196ae10b ("net/tap: use new Rx offloads API")
>> Fixes: 818fe14a9891 ("net/tap: use new Tx offloads API")
>> Cc: motih@mellanox.com
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
>
>
next prev parent reply other threads:[~2018-04-12 16:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 18:28 Ferruh Yigit
2018-04-05 17:49 ` Thomas Monjalon
2018-04-12 16:23 ` Ferruh Yigit [this message]
2018-04-18 8:59 ` Ferruh Yigit
2018-04-18 9:40 ` Ophir Munk
2018-04-18 10:55 ` Ferruh Yigit
2018-04-22 16:04 ` Ophir Munk
2018-04-23 8:39 ` Ophir Munk
2018-04-23 9:17 ` Ophir Munk
2018-04-23 10:13 ` Ferruh Yigit
2018-04-23 11:32 ` Ophir Munk
2018-04-24 17:57 ` Ferruh Yigit
2018-04-23 9:38 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-04-24 17:54 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2018-04-25 9:18 ` Ophir Munk
2018-04-25 9:48 ` Ferruh Yigit
2018-04-25 12:00 ` Ophir Munk
2018-04-25 12:20 ` Ophir Munk
2018-04-25 16:17 ` Ophir Munk
2018-04-25 17:18 ` 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=e2cea389-14ac-2aeb-0426-d20b692e2ebe@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=motih@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).