DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "Varghese, Vipin" <vipin.varghese@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Patel, Amol" <amol.patel@intel.com>,
	"Hunt, David" <david.hunt@intel.com>,
	"Jain, Deepak K" <deepak.k.jain@intel.com>,
	Pascal Mazon <pascal.mazon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v1] [net/tap] add logic to assign speed from user
Date: Wed, 17 Jan 2018 16:22:47 +0000	[thread overview]
Message-ID: <6dd432ff-575f-4fa1-e65f-f707bef06216@intel.com> (raw)
In-Reply-To: <92A6F8C2-94CF-404D-9970-5357CEA79277@intel.com>

On 1/17/2018 4:14 PM, Wiles, Keith wrote:
> 
> 
>> On Jan 17, 2018, at 10:06 AM, Yigit, Ferruh <ferruh.yigit@intel.com> wrote:
>>
>> On 12/21/2017 1:38 PM, Wiles, Keith wrote:
>>>
>>>
>>>> On Dec 21, 2017, at 10:53 AM, Vipin Varghese <vipin.varghese@intel.com> wrote:
>>>>
>>>> TAP speed is passed as user argument, but never set to interface.
>>>> New logic brings speed get and set to LOCAL and REMOTE interfaces.
>>>>
>>>> Updated the default PMD speeed to 10M as per Linux Kernel default
>>>> value.
>>>
>>> The problem in setting the link speed to 10M is that TAP will not limit its traffic to 10M. Applications like pktgen and others use the Link speed to calculate the bit rate, which will be broken now.
>>>
>>> I would suggest making the default value 10G or 40G instead as CPU speeds will continue to increase. Forcing someone to always add the link speed seems a bit much when we know the systems can send/receive much higher then 10M, which is the reason 10G was picked. Please set the default back to 10G or some much higher number.
>>
>> Hi Keith, Vipin, Pascal,
>>
>> Since we really can't set the interface for Linux tap interface, what do you
>> think removing speed arg completely from tap PMD?
> 
> I have no problems with it being remove from the PMD. The only problem is this being a virtual interface it can be any speed, but 10M is unreasonable IMO. I would like it to be set to something reasonable as the default (40G or 10G) or would zero be more reasonable.

Agreed.
When "speed" arg removed I think there is no reason to change default speed, it
can stay as 10G as it is now.

> 
> I know the reported speed does not effect the performance, but tools that look at the speed and attempt to use that speed need a value greater then the max bit rate of the interface IMO. If we had a value to indicate a bogus speed then maybe the tools can adjust in some way.
> 
>>
>> Thanks,
>> ferruh
>>
>>>
>>>>
>>>> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
>>>> ---
>>>> drivers/net/tap/rte_eth_tap.c | 185 +++++++++++++++++++++++++++++++++++++++++-
>>>> 1 file changed, 182 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
>>>> index 6b27679..7238504 100644
>>>> --- a/drivers/net/tap/rte_eth_tap.c
>>>> +++ b/drivers/net/tap/rte_eth_tap.c
>>>> @@ -62,6 +62,8 @@
>>>> #include <linux/if_ether.h>
>>>> #include <linux/version.h>
>>>> #include <fcntl.h>
>>>> +#include <linux/ethtool.h>
>>>> +#include <linux/sockios.h>
>>>>
>>>
>>> Regards,
>>> Keith
> 
> Regards,
> Keith
> 

  reply	other threads:[~2018-01-17 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 16:53 Vipin Varghese
2017-12-21 13:38 ` Wiles, Keith
2018-01-17 16:06   ` Ferruh Yigit
2018-01-17 16:14     ` Wiles, Keith
2018-01-17 16:22       ` Ferruh Yigit [this message]
2018-01-18 14:04         ` Pascal Mazon

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=6dd432ff-575f-4fa1-e65f-f707bef06216@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amol.patel@intel.com \
    --cc=david.hunt@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=pascal.mazon@6wind.com \
    --cc=vipin.varghese@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).