From: zhuyj <zyjzyj2000@gmail.com>
To: "Tao, Yue" <Yue.Tao@windriver.com>,
linux-kernel@vger.kernel.org, jasowang@redhat.com,
Willy Tarreau <w@1wt.eu>,
"Yang, Zhangle (Eric)" <Zhangle.Yang@windriver.com>,
zhuyj <zyjzyj2000@gmail.com>
Subject: Re: in kernel 2.6.x, tun/tap nic supports vlan packets
Date: Thu, 17 Apr 2014 14:27:16 +0800 [thread overview]
Message-ID: <534F7444.4010502@gmail.com> (raw)
In-Reply-To: <534F4C1E.1000006@gmail.com>
Hi, Jaso
Would you like to code review these 2 patches?
Thanks a lot.
Zhu Yanjun
On 04/17/2014 11:35 AM, zhuyj wrote:
> Hi, all
>
> In kernel 2.6.x, linux depends on nic vlan hardware acceleration to
> insert/extract
> vlan tag. In this scene, in kernel 2.6.x
>
> _____ ________
> A | | B | | C
> vlan packets-->| tap |----->|vlan nic|--->
> |_____| |________|
>
> We hope vlan packets pass through tap and vlan nic from A to c.
> But in kernel 2.6.x, linux kernel can not extract vlan tag. It depends
> on nic vlan hardware acceleration. It is well known that tap nic has no
> vlan acceleration. So in the above scene, vlan packets can not be
> handled by
> tap nic. These vlan packets will be discarded in B. They can not
> arrive at C.
>
> In kernel 3.x, linux can handle vlan packets. It does not depend on
> nic vlan
> hardware acceleration. So the above scene can work well in kernel 3.x.
>
> To resolve the above in kernel 2.6.x, we simulated vlan hardware
> acceleration in
> tun/tap driver. Then followed the logic of commit commit 4fba4ca4
> [vlan: Centralize handling of hardware acceleration] to modify the
> vlan packets
> process in kernel 2.6.x. In the end, the above scene can work well in
> patched
> kernel 2.6.x.
>
> Please comment on it. Any reply is appreciated.
>
> Hi, Willy
>
> These 2 patches are for linux2.6.x. These can work well here. Please
> help to merge
> linux 2.6.32.x. Thanks a lot.
>
> Best Regards!
> Zhu Yanjun
>
next prev parent reply other threads:[~2014-04-17 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 3:35 in kernel 2.6.x, tun/tap nic supports vlan packets zhuyj
2014-04-17 5:02 ` Willy Tarreau
2014-04-17 5:50 ` zhuyj
2014-04-19 13:43 ` zhuyj
2014-04-22 17:53 ` Ben Hutchings
2014-04-23 7:48 ` zhuyj
2014-04-23 11:41 ` Ben Hutchings
2014-04-24 2:10 ` zhuyj
2014-04-24 5:24 ` Willy Tarreau
2014-04-25 8:09 ` zhuyj
2014-04-17 6:27 ` zhuyj [this message]
2014-04-17 13:52 ` zhuyj
2014-04-17 14:23 ` Willy Tarreau
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=534F7444.4010502@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=Yue.Tao@windriver.com \
--cc=Zhangle.Yang@windriver.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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.