From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, eric.dumazet@gmail.com,
davem@davemloft.net
Subject: Re: [PATCHv2 net-next 4/4] macvtap: Perform GSO on forwarding path.
Date: Wed, 26 Jun 2013 00:25:28 +0400 [thread overview]
Message-ID: <51C9FCB8.7070201@cogentembedded.com> (raw)
In-Reply-To: <1372190662-30815-5-git-send-email-vyasevic@redhat.com>
Hello.
On 06/26/2013 12:04 AM, Vlad Yasevich wrote:
> When macvtap forwards skb to its tap, it needs to check
> if GSO needs to be performed. This is sometimes necessary
> when the HW device performed GRO, but the guest reading
> from the tap does not support it (ex: Windows 7).
> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
> ---
> drivers/net/macvtap.c | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index 7eab019..e370b79 100644
> --- a/drivers/net/macvtap.c
> +++ b/drivers/net/macvtap.c
> @@ -276,14 +276,43 @@ static void macvtap_del_queues(struct net_device *dev)
> */
> static int macvtap_forward(struct net_device *dev, struct sk_buff *skb)
> {
> + struct macvlan_dev *vlan = netdev_priv(dev);
> struct macvtap_queue *q = macvtap_get_queue(dev, skb);
> + netdev_features_t features;
> if (!q)
> goto drop;
>
> if (skb_queue_len(&q->sk.sk_receive_queue) >= dev->tx_queue_len)
> goto drop;
>
> - skb_queue_tail(&q->sk.sk_receive_queue, skb);
> + skb->dev = dev;
> + /* Apply the forward feature mask so that we perform segmentation
> + * according to users wishes.
> + */
> + features = netif_skb_features(skb) & vlan->tap_features;
> + if (netif_needs_gso(skb, features)) {
> + struct sk_buff *segs = __skb_gso_segment(skb, features, false);
> +
> + if (IS_ERR(segs))
> + goto drop;
> +
> + if (!segs) {
> + skb_queue_tail(&q->sk.sk_receive_queue, skb);
> + goto wake_up;
> + }
> +
> + kfree_skb(skb);
> + while (segs) {
> + struct sk_buff *nskb = segs->next;
> +
> + segs->next = NULL;
> + skb_queue_tail(&q->sk.sk_receive_queue, segs);
> + segs = nskb;
> + }
> + } else
> + skb_queue_tail(&q->sk.sk_receive_queue, skb);
According to Documentation/CodingStyle chapter 3, you should have {}
on both branches of *if* statement, if one branch has it.
WBR, Sergei
next prev parent reply other threads:[~2013-06-25 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 20:04 [PATCHv2 net-next 0/4] macvtap: locking and offload control Vlad Yasevich
2013-06-25 20:04 ` [PATCHv2 net-next 1/4] macvtap: Convert to using rtnl lock Vlad Yasevich
2013-06-25 20:31 ` Eric Dumazet
2013-06-25 20:04 ` [PATCHv2 net-next 2/4] macvtap: Consistently use rcu functions Vlad Yasevich
2013-06-25 20:31 ` Eric Dumazet
2013-06-25 20:04 ` [PATCHv2 net-next 3/4] macvtap: Let TUNSETOFFLOAD actually controll offload features Vlad Yasevich
2013-06-25 20:04 ` [PATCHv2 net-next 4/4] macvtap: Perform GSO on forwarding path Vlad Yasevich
2013-06-25 20:25 ` Sergei Shtylyov [this message]
2013-06-25 23:46 ` David Miller
2013-06-25 23:45 ` [PATCHv2 net-next 0/4] macvtap: locking and offload control David Miller
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=51C9FCB8.7070201@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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).