[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110714.170506.1425372007221475085.davem@davemloft.net>
Date: Thu, 14 Jul 2011 17:05:06 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mirq-linux@...e.qmqm.pl
Cc: therbert@...gle.com, bhutchings@...arflare.com,
netdev@...r.kernel.org
Subject: Re: [PATCH 07/10] net: remove NETIF_F_NO_CSUM feature
From: Michaİİ Mirosİİaw <mirq-linux@...e.qmqm.pl>
Date: Fri, 15 Jul 2011 00:44:45 +0200
> On Thu, Jul 14, 2011 at 02:31:21PM -0700, David Miller wrote:
>> From: Michaİİ Mirosİİaw <mirq-linux@...e.qmqm.pl>
>> Date: Thu, 14 Jul 2011 22:56:23 +0200
>> > That's why its turned off by default and should be enabled only when user
>> > knows he will win some pps with it.
>> More people are going to lose than win by your change.
>>
>> The nocopy feature helps more real situations than it hurts, the
>> existing default is the best.
>
> I see. I still want to remove NO_CSUM (as I explained in other mail),
> so would you accept replacing it with something more specific to
> nocache-copy feature? READS_DATA maybe? That could be later added to
> sk_route_caps whenever it's known for a route there will be need to
> read packets' data.
I don't actually see what the problem is.
The code wants to conditionalize the nocache-copy feature based upon
whether hardware will checksum the packet or not.
And that's exactly what it's testing.
The reason, of course, is because it doesn't want to enable
nocache-copy if the cpu is just going to read the data back into it's
caches during the checksum. But that's no reason to change the
flag name to have the word "read" instead of "checksum" in it.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists