netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: zhuyj <zyjzyj2000@gmail.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: take care of bonding in build_skb_flow_key
Date: Wed, 6 Jan 2016 15:11:35 +0800	[thread overview]
Message-ID: <568CBE27.7030004@oracle.com> (raw)
In-Reply-To: <568CB7EB.7080705@gmail.com>

Hmm, we are not changing device MTU but PMTU...

thanks,
wengang

在 2016年01月06日 14:44, zhuyj 写道:
> IMHO, the following comments will help us all.
>
>         case NETDEV_CHANGEMTU:
>                 /* TODO: Should slaves be allowed to
>                  * independently alter their MTU?  For
>                  * an active-backup bond, slaves need
>                  * not be the same type of device, so
>                  * MTUs may vary.  For other modes,
>                  * slaves arguably should have the
>                  * same MTUs. To do this, we'd need to
>                  * take over the slave's change_mtu
>                  * function for the duration of their
>                  * servitude.
>                  */
>                 break;
>
> Best Regards!
> Zhu Yanjun
>
> On 01/06/2016 02:32 PM, Wengang Wang wrote:
>>
>>
>> 在 2016年01月06日 14:18, David Miller 写道:
>>> From: Wengang Wang <wen.gang.wang@oracle.com>
>>> Date: Wed,  6 Jan 2016 13:49:28 +0800
>>>
>>>> @@ -523,11 +523,20 @@ static void build_skb_flow_key(struct flowi4 
>>>> *fl4, const struct sk_buff *skb,
>>>>                      const struct sock *sk)
>>>>   {
>>>>       const struct iphdr *iph = ip_hdr(skb);
>>>> -    int oif = skb->dev->ifindex;
>>>> +    int oif;
>>>> +    struct net_device *master = NULL;
>>>> +
>>>>       u8 tos = RT_TOS(iph->tos);
>>>>       u8 prot = iph->protocol;
>>>>       u32 mark = skb->mark;
>>> Please fix the stlye of these variable declarations:
>>>
>>> 1) Order them from longest line to shortest line, also known
>>>     as "reverse christmas tree" layout.
>>>
>>> 2) Do not add an empty line in the middle of these variable
>>>     declarations.
>> OK, will do in second drop.
>>
>> thanks,
>> wengang
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-01-06  7:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06  5:49 [PATCH] net: take care of bonding in build_skb_flow_key Wengang Wang
2016-01-06  6:18 ` David Miller
2016-01-06  6:32   ` Wengang Wang
2016-01-06  6:44     ` zhuyj
2016-01-06  7:11       ` Wengang Wang [this message]
2016-01-06  6:19 ` zhuyj
2016-01-06  7:06   ` Wengang Wang
2016-01-06  7:35     ` zhuyj
2016-01-06  7:45       ` Wengang Wang
2016-01-06  8:00         ` zhuyj
2016-01-06  8:14           ` Wengang Wang
2016-01-06  8:18             ` zhuyj
2016-01-06  9:04               ` Wengang Wang

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=568CBE27.7030004@oracle.com \
    --to=wen.gang.wang@oracle.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=zyjzyj2000@gmail.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).