From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: jesse@nicira.com, pshelar@nicira.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] IP_GRE: Linearize skb before csum.
Date: Tue, 22 Jan 2013 19:41:43 -0500 (EST) [thread overview]
Message-ID: <20130122.194143.1205292712415183747.davem@davemloft.net> (raw)
In-Reply-To: <1358894653.12374.201.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 22 Jan 2013 14:44:13 -0800
> On Tue, 2013-01-22 at 14:38 -0800, Jesse Gross wrote:
>
>>
>> We're currently enforcing this assumption in the rest of the network
>> stack - it's why we mask out scatter/gather capability in the NIC if
>> it isn't capable of checksumming the packet.
>>
>> Packets with asynchronous changes may come from VMs, so it isn't
>> necessarily reasonable to tell people that they need to disable
>> offloads with certain use cases.
>>
>> As Pravin said, pushing down the GSO to the lowest layer is the best
>> way to solve the problem. However, I would argue that the current
>> behavior is not correct.
>
> You do understand this problem is generic to GSO ?
>
> You basically are saying GSO should be removed.
>
> If you really care, please find another way to address the problem.
>
> Frames build by tcp_sendmsg() are fine : their content cannot be changed
> by the user.
We don't emit crap onto the wire knowingly. Jesse is right.
If you want to do software GSO in situations where we know that the
paged data cannot be modified asynchronously, you'll have to
explicitly support that.
I will not accept us saying that allowing the emission of bad
checksums is OK. It never is. That's terrible behavior, and creates
impossible to disagnose problems.
next prev parent reply other threads:[~2013-01-23 0:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 21:20 [PATCH 2/2] IP_GRE: Linearize skb before csum Pravin B Shelar
2013-01-22 22:03 ` Eric Dumazet
2013-01-22 22:08 ` David Miller
2013-01-22 22:15 ` Eric Dumazet
2013-01-22 22:30 ` Pravin Shelar
2013-01-22 22:38 ` Jesse Gross
2013-01-22 22:44 ` Eric Dumazet
2013-01-23 0:41 ` David Miller [this message]
2013-01-23 1:08 ` Eric Dumazet
2013-01-23 1:46 ` David Miller
2013-01-23 4:22 ` David Miller
2013-01-23 5:02 ` Eric Dumazet
2013-01-23 5:19 ` David Miller
2013-01-23 5:30 ` Eric Dumazet
2013-01-23 5:36 ` 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=20130122.194143.1205292712415183747.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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).