From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Tiwei Bie <tiwei.bie@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/vhost: convert to new Rx/Tx offload API
Date: Tue, 22 May 2018 14:48:17 +0200 [thread overview]
Message-ID: <6b9a655f-deb9-8f63-948a-c21f80fc7c4c@redhat.com> (raw)
In-Reply-To: <288d7bb4-f8bd-22e8-8664-19ad1b273846@intel.com>
On 05/22/2018 02:38 PM, Ferruh Yigit wrote:
> On 5/22/2018 1:34 PM, Tiwei Bie wrote:
>> On Tue, May 22, 2018 at 02:22:11PM +0200, Maxime Coquelin wrote:
>>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>>> ---
>>> Changes since v2:
>>> - Announce supported Rx & Tx offload features (Tiwei)
>>>
>>> drivers/net/vhost/rte_eth_vhost.c | 8 ++++++--
>>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/net/vhost/rte_eth_vhost.c b/drivers/net/vhost/rte_eth_vhost.c
>>> index f473bbbb3..229a5ba8d 100644
>>> --- a/drivers/net/vhost/rte_eth_vhost.c
>>> +++ b/drivers/net/vhost/rte_eth_vhost.c
>>> @@ -491,9 +491,9 @@ eth_dev_configure(struct rte_eth_dev *dev __rte_unused)
>>> struct pmd_internal *internal = dev->data->dev_private;
>>> const struct rte_eth_rxmode *rxmode = &dev->data->dev_conf.rxmode;
>>>
>>> - internal->vlan_strip = rxmode->hw_vlan_strip;
>>> + internal->vlan_strip = !!(rxmode->offloads & DEV_RX_OFFLOAD_VLAN_STRIP);
>>>
>>> - if (rxmode->hw_vlan_filter)
>>> + if (rxmode->offloads & DEV_RX_OFFLOAD_VLAN_FILTER)
>>> VHOST_LOG(WARNING,
>>> "vhost(%s): vlan filtering not available\n",
>>> internal->dev_name);
>>
>> I'm not quite sure whether we still need to log this warning.
>
> Similar warning exists in ethdev layer, when an offload requested that is not
> reported in capability. So I agree to remove this.
>
> And in next release that warning will be converted into error, so that PMD will
> not get those values at all.
Ok, I'll post a v3 removing the check.
Thanks,
Maxime
>>
>>> @@ -1072,6 +1072,10 @@ eth_dev_info(struct rte_eth_dev *dev,
>>> dev_info->max_rx_queues = internal->max_queues;
>>> dev_info->max_tx_queues = internal->max_queues;
>>> dev_info->min_rx_bufsize = 0;
>>> +
>>> + dev_info->tx_offload_capa = DEV_TX_OFFLOAD_MULTI_SEGS |
>>> + DEV_TX_OFFLOAD_VLAN_INSERT;
>>> + dev_info->rx_offload_capa = DEV_RX_OFFLOAD_VLAN_STRIP;
>>> }
>>
>> Other than that, it looks good to me. Thanks!
>>
>> Best regards,
>> Tiwei Bie
>>
>
prev parent reply other threads:[~2018-05-22 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 12:22 Maxime Coquelin
2018-05-22 12:34 ` Tiwei Bie
2018-05-22 12:37 ` Maxime Coquelin
2018-05-22 12:38 ` Ferruh Yigit
2018-05-22 12:48 ` Maxime Coquelin [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=6b9a655f-deb9-8f63-948a-c21f80fc7c4c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=tiwei.bie@intel.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).