From: Victor Julien <victor@inliniac.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kuba@kernel.org, corbet@lwn.net,
edumazet@google.com, willemb@google.com, maowenan@huawei.com,
arnd@arndb.de, nhorman@tuxdriver.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] af-packet: new flag to indicate all csums are good
Date: Tue, 2 Jun 2020 06:23:54 +0200 [thread overview]
Message-ID: <11986598-9357-dfdd-e187-c9eb0428fd62@inliniac.net> (raw)
In-Reply-To: <20200601.144535.203726078659236025.davem@davemloft.net>
On 01-06-2020 23:45, David Miller wrote:
> From: Victor Julien <victor@inliniac.net>
> Date: Mon, 1 Jun 2020 22:49:37 +0200
>
>> @@ -472,6 +472,12 @@ TP_STATUS_CSUM_VALID This flag indicates that at least the transport
>> validated on the kernel side. If the flag is not set
>> then we are free to check the checksum by ourselves
>> provided that TP_STATUS_CSUMNOTREADY is also not set.
>> +TP_STATUS_CSUM_UNNECESSARY This flag indicates that the driver validated all
>> + the packets csums. If it is not set it might be that
>> + the driver doesn't support this, or that one of the
>> + layers csums is bad. TP_STATUS_CSUM_VALID may still
>> + be set if the transport layer csum is correct or
>> + if the driver supports only this mode.
>> ====================== =======================================================
> ^^^^^
>
> I think you need to reformat these dividers.
>
Yes of course. Think I'll have to reformat the whole table then, at
least for `rst2pdf` to accept it.
Alternatively I can try to come up with a shorter name for the flag, but
I'm not really coming up with anything so far.
--
---------------------------------------------
Victor Julien
http://www.inliniac.net/
PGP: http://www.inliniac.net/victorjulien.asc
---------------------------------------------
prev parent reply other threads:[~2020-06-02 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 20:49 Victor Julien
2020-06-01 21:45 ` David Miller
2020-06-02 4:23 ` Victor Julien [this message]
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=11986598-9357-dfdd-e187-c9eb0428fd62@inliniac.net \
--to=victor@inliniac.net \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maowenan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=willemb@google.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
all inboxes | Powered by JetHome®