From: Francois Romieu <romieu@fr.zoreil.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>,
"Linux 802.1Q VLAN" <vlan@candelatech.com>
Subject: Re: [PATCH] 802.1Q VLAN
Date: Fri, 22 Oct 2004 23:46:11 +0200 [thread overview]
Message-ID: <20041022214611.GA4948@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <41797696.9070905@candelatech.com>
Minor nits below.
[...]
> @@ -484,13 +484,32 @@
> veth->h_vlan_proto, veth->h_vlan_TCI,
> veth->h_vlan_encapsulated_proto);
> #endif
>
> - stats->tx_packets++; /* for statics only */
> - stats->tx_bytes += skb->len;
> -
> skb->dev = VLAN_DEV_INFO(dev)->real_dev;
> - dev_queue_xmit(skb);
>
> - return 0;
> + {
> + /* Please note, dev_queue_xmit consumes the pkt regardless of the
> + * error value. So, will copy the skb first and free if successful.
> + */
> + struct sk_buff* skb2 = skb_get(skb);
> + int rv = dev_queue_xmit(skb2);
> + if (rv != 0) {
> + /* The skb memory should still be valid since we made a copy,
> + * so can return error code here.
> + */
> + return rv;
> + }
> + else {
> + /* Was success, need to free the skb reference since we bumped up the
> + * user count above.
> + */
> +
> + stats->tx_packets++; /* for statics only */
> + stats->tx_bytes += skb->len;
> +
> + kfree_skb(skb);
> + return 0;
> + }
> + }
Why not use a single return point, say:
struct sk_buff *skb2 = skb_get(skb);
int rv = dev_queue_xmit(skb2);
if (!rv) {
/*
* Was success, need to free the skb reference since
* we bumped up the user count above.
*/
stats->tx_packets++; /* for statics only */
stats->tx_bytes += skb->len;
kfree_skb(skb);
}
return rv;
vlan_dev_get_realdev_name() and vlan_dev_get_vid() can be tidy up
a bit (factoring dev_put() or handling debug code differently for instance).
[...]
> --- linux-2.6.9/include/linux/if_vlan.h 2004-10-18
> 14:53:43.000000000 -0700
> +++ linux-2.6.9.p4s/include/linux/if_vlan.h 2004-10-22
> 12:14:24.000000000 -0700
> @@ -366,7 +366,9 @@
> GET_VLAN_INGRESS_PRIORITY_CMD,
> GET_VLAN_EGRESS_PRIORITY_CMD,
> SET_VLAN_NAME_TYPE_CMD,
> - SET_VLAN_FLAG_CMD
> + SET_VLAN_FLAG_CMD,
> + GET_VLAN_REALDEV_NAME_CMD, /* If this works, you know it's a VLAN device, btw */
> + GET_VLAN_VID_CMD /* Get the VID of this VLAN (specified by name) */
> };
Whitespace attacks.
My 0.02 U+20AC
--
Ueimor
next prev parent reply other threads:[~2004-10-22 21:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 21:07 [PATCH] 802.1Q VLAN Ben Greear
2004-10-22 21:46 ` Francois Romieu [this message]
2004-10-22 22:09 ` Ben Greear
2004-10-23 0:24 ` Francois Romieu
2004-10-25 20:51 ` Ben Greear
2004-10-25 23:56 ` Ben Greear
2004-10-27 1:02 ` David S. Miller
2004-10-27 23:49 ` David S. Miller
2004-10-28 1:28 ` Ben Greear
2004-10-28 4:42 ` David S. Miller
2004-10-28 23:40 ` Tommy Christensen
2004-10-28 23:35 ` David S. Miller
2004-10-29 0:23 ` Ben Greear
2004-10-29 0:38 ` Krzysztof Halasa
2004-10-29 8:29 ` Tommy Christensen
2004-10-29 17:45 ` Ben Greear
2004-10-29 23:37 ` Tommy Christensen
2004-10-29 23:56 ` Ben Greear
2004-10-30 0:05 ` Ben Greear
2004-10-30 0:31 ` Tommy Christensen
2004-11-01 18:58 ` Ben Greear
2004-11-01 23:08 ` Tommy Christensen
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=20041022214611.GA4948@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=vlan@candelatech.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).