netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	"Maciej Żenczykowski" <maze@google.com>,
	"Florian Westphal" <fw@strlen.de>,
	"Eric Dumazet" <eric.dumazet@gmail.com>
Subject: Re: [Patch net-next] net: rename local_df to ignore_df
Date: Mon, 5 May 2014 01:54:36 +0200	[thread overview]
Message-ID: <20140504235436.GA32448@breakpoint.cc> (raw)
In-Reply-To: <1399246758-29795-1-git-send-email-xiyou.wangcong@gmail.com>

Cong Wang <xiyou.wangcong@gmail.com> wrote:
> As suggested by several people, rename local_df to ignore_df,
> since it means "ignore df bit if it is set".

Thanks for doing this.

David, this has small conflict with a patch I sent couple of hours ago.

Also, I do have another bug fix patch that will move a function
evaluating skb->local_df around [ ie. targeted at net tree ]

That patch needs more testing but I will send it within next 30 hours.

> diff --git a/net/ipv4/ip_forward.c b/net/ipv4/ip_forward.c
> index be8abe7..8ac422f 100644
> --- a/net/ipv4/ip_forward.c
> +++ b/net/ipv4/ip_forward.c
> @@ -42,12 +42,12 @@
>  static bool ip_may_fragment(const struct sk_buff *skb)
>  {
>  	return unlikely((ip_hdr(skb)->frag_off & htons(IP_DF)) == 0) ||
> -	       !skb->local_df;
> +	       !skb->ignore_df;

nicely illustrates why the rename is a good idea, IMO.

[ should read '|| skb->ignore_df', the negation is wrong ]

  reply	other threads:[~2014-05-04 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 23:39 [Patch net-next] net: rename local_df to ignore_df Cong Wang
2014-05-04 23:54 ` Florian Westphal [this message]
2014-05-05  3:03 ` Maciej Żenczykowski
2014-05-07 19:30 ` David Miller
2014-05-07 20:49   ` Maciej Żenczykowski
2014-05-09  4:40   ` Cong 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=20140504235436.GA32448@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@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).