Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= <toke@toke.dk>,
	"Cake List" <cake@lists.bufferbloat.net>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Cake] [Ecn-sane]  l4s kernel submission
Date: Sat, 16 Oct 2021 19:57:03 -0400	[thread overview]
Message-ID: <8788.1634428623@localhost> (raw)
In-Reply-To: <CAA93jw7kwCc9HmfA7X4BzSCS+9UgngXj31d3gb7Aw=XQtQHZMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]


Dave Taht <dave.taht@gmail.com> wrote:
    > What happens when a GSO packet is marked? Do all the packets get the
    > marking, or just the first?

Having done no work in this area for over a decade.... I think that the GSO
marking is in the skb (which is a Linux-ism, obviously), which goes down into
the device-specific driver, who then loads the single packet into the device
queue, and marks the packet for GSO in a device-specific way in the ring
descriptor.

The device does the Segment Offload.  There is no marking relevant in the
packet itself. There aren't multiple skb's for the packet.

So I think that the answer is "mu"

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide





[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2021-10-16 23:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 20:06 [Cake] " Dave Taht
2021-10-14 20:31 ` Sebastian Moeller
2021-10-14 21:27   ` Dave Taht
2021-10-14 21:44     ` [Cake] [Ecn-sane] " Toke Høiland-Jørgensen
2021-10-14 22:00       ` Dave Taht
2021-10-14 22:10         ` Toke Høiland-Jørgensen
2021-10-14 22:17           ` Dave Taht
2021-10-16  8:04             ` Jonathan Morton
2021-10-16  8:38               ` Sebastian Moeller
2021-10-16  8:54                 ` Jonathan Morton
2021-10-16 10:29                   ` Sebastian Moeller
2021-10-16 12:49                   ` Sebastian Moeller
2021-10-16 16:58               ` Rodney W. Grimes
2021-10-16 21:01             ` Dave Taht
2021-10-16 23:57               ` Michael Richardson [this message]
2021-10-18 13:02               ` Toke Høiland-Jørgensen
2021-10-19  2:45                 ` Dave Taht
2021-10-19 11:19                   ` Toke Høiland-Jørgensen
2021-10-19 13:30                     ` Dave Taht
2021-10-19 13:34                       ` Sebastian Moeller
2021-10-19 14:16                         ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8788.1634428623@localhost \
    --to=mcr+ietf@sandelman.ca \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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