All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Zhu Yanjun <Yanjun.Zhu@windriver.com>,
	netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
	viro@zeniv.linux.org.uk, davem@davemloft.net,
	jonathon.reinhart@gmail.com
Subject: Re: [PATCH 1/1] tun: change speed from 10M to dynamically configured
Date: Fri, 13 Feb 2015 13:45:09 +0300	[thread overview]
Message-ID: <54DDD5B5.2050605@cogentembedded.com> (raw)
In-Reply-To: <1423808353-8722-2-git-send-email-Yanjun.Zhu@windriver.com>

On 2/13/2015 9:19 AM, Zhu Yanjun wrote:

> The default speed of normal nic is 1000M while the default speed
> of tun is 10M. Now the default speed of tun is changed to 1000M.
> And there are 3 options: 10M, 100M and 1000M to the speed of tun.
> The command "ethtool -s tun0 speed 10/100/1000" can configure the
> speed of tun dynamically.

> CC: Michael S. Tsirkin <mst@redhat.com>
> CC: Jason Wang <jasowang@redhat.com>
> CC: Al Viro <viro@zeniv.linux.org.uk>
> Reviewed-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Reviewed-by: Jonathon Reinhart <jonathon.reinhart@gmail.com>
> Signed-off-by: Zhu Yanjun <Yanjun.Zhu@windriver.com>

[...]

> diff --git a/include/uapi/linux/if_tun.h b/include/uapi/linux/if_tun.h
> index 50ae243..78a09a7 100644
> --- a/include/uapi/linux/if_tun.h
> +++ b/include/uapi/linux/if_tun.h
> @@ -66,6 +66,11 @@
>   #define IFF_PERSIST	0x0800
>   #define IFF_NOFILTER	0x1000
>
> +/*add speed control, default 1000M*/

    Please do add spaces after /* and before */.

> +#define TUN_CTRL_SPD_10         0x0020
> +#define TUN_CTRL_SPD_100        0x0040
> +#define TUN_CTRL_SPD_1000       0x0080
> +
>   /* Socket options */
>   #define TUN_TX_TIMESTAMP 1

WBR, Sergei

  parent reply	other threads:[~2015-02-13 10:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13  6:19 [PATCH V3 0/1] tun: dynamically set speed of tun Zhu Yanjun
2015-02-13  6:19 ` [PATCH 1/1] tun: change speed from 10M to dynamically configured Zhu Yanjun
2015-02-13 10:03   ` yzhu1
2015-02-13 10:45   ` Sergei Shtylyov [this message]
2015-02-13 21:28   ` Francois Romieu
2015-02-13 21:32     ` Rick Jones
2015-02-13 23:15       ` Francois Romieu
2015-02-16  2:31     ` yzhu1
2015-02-16 17:03       ` Stephen Hemminger
2015-02-18 19:29         ` Andy Gospodarek
2015-02-18 19:39         ` Andy Gospodarek
2015-02-19 20:37           ` David Miller
2015-02-19 20:40         ` David Miller
2015-02-20  0:41           ` Simon Horman
2015-02-20  2:35           ` Andy Gospodarek
2015-02-20 20:07             ` David Miller
2015-02-21  3:07               ` Andy Gospodarek
2015-02-20 10:01           ` David Laight
2015-02-19 20:56         ` roopa
  -- strict thread matches above, loose matches on Subject: below --
2015-02-12  5:35 [PATCH 0/1] tun: dynamically set speed of tun Zhu Yanjun
2015-02-12  5:35 ` [PATCH 1/1] tun: change speed from 10M to dynamically configured Zhu Yanjun
2015-02-12 12:55   ` Stephen Hemminger
2015-02-13  2:45     ` yzhu1
2015-02-13  3:25       ` Fan Du
2015-02-13  3:34         ` yzhu1
2015-02-12 13:52   ` Sergei Shtylyov

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=54DDD5B5.2050605@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=Yanjun.Zhu@windriver.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=jonathon.reinhart@gmail.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.