From: Ben Hutchings <bhutchings@solarflare.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] gre: fix spelling in comments
Date: Fri, 24 Feb 2012 19:17:25 +0000 [thread overview]
Message-ID: <1330111045.2397.14.camel@bwh-desktop> (raw)
In-Reply-To: <20120224100820.227ed31c@nehalam.linuxnetplumber.net>
On Fri, 2012-02-24 at 10:08 -0800, Stephen Hemminger wrote:
> The original spelling and bad word choice makes these comments hard to read.
Not to mention weird capitalisation.
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
> --- a/net/ipv4/ip_gre.c 2012-02-24 10:04:41.007678920 -0800
> +++ b/net/ipv4/ip_gre.c 2012-02-24 10:07:54.421769389 -0800
> @@ -65,7 +65,7 @@
> it is infeasible task. The most general solutions would be
> to keep skb->encapsulation counter (sort of local ttl),
'ttl' is an abbreviation, and not a variable name here, so should be
capitalised.
> and silently drop packet when it expires. It is a good
> - solution, but it supposes maintaing new variable in ALL
> + solution, but it supposes maintaining new variable in ALL
> skb, even if no tunneling is used.
>
> Current solution: xmit_recursion breaks dead loops. This is a percpu
> @@ -91,14 +91,14 @@
>
> One of them is to parse packet trying to detect inner encapsulation
> made by our node. It is difficult or even impossible, especially,
> - taking into account fragmentation. TO be short, tt is not solution at all.
> + taking into account fragmentation. TO be short, ttl is not solution at all.
'TO' shouldn't be capitalised.
>
> Current solution: The solution was UNEXPECTEDLY SIMPLE.
'UNEXPECTEDLY SIMPLE' shouldn't be capitalised. Also, after the passage
of a few years, this is perhaps no longer unexpected at all...
> We force DF flag on tunnels with preconfigured hop limit,
> that is ALL. :-) Well, it does not remove the problem completely,
> but exponential growth of network traffic is changed to linear
> (branches, that exceed pmtu are pruned) and tunnel mtu
'pmtu' and 'mtu' should be capitalised.
> - fastly degrades to value <68, where looping stops.
> + rapidly degrades to value <68, where looping stops.
> Yes, it is not good if there exists a router in the loop,
> which does not force DF, even when encapsulating packets have DF set.
> But it is not our problem! Nobody could accuse us, we made
> @@ -457,8 +457,8 @@ static void ipgre_err(struct sk_buff *sk
> GRE tunnels with enabled checksum. Tell them "thank you".
>
> Well, I wonder, rfc1812 was written by Cisco employee,
'rfc' should be capitalised.
> - what the hell these idiots break standrads established
> - by themself???
> + what the hell these idiots break standards established
> + by themselves???
> */
>
> const struct iphdr *iph = (const struct iphdr *)skb->data;
Insults also detract from the readability as a technical description.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-02-24 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 18:08 [PATCH] gre: fix spelling in comments Stephen Hemminger
2012-02-24 19:17 ` Ben Hutchings [this message]
2012-02-24 19:29 ` Stephen Hemminger
2012-02-24 22:39 ` David Miller
2012-02-24 22:41 ` 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=1330111045.2397.14.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).