From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Thorsten Glaser <t.glaser@tarent.de>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Haye.Haehne@telekom.de
Subject: Re: knob to disable locally-originating qdisc optimisation?
Date: Wed, 17 May 2023 12:00:26 +0200 [thread overview]
Message-ID: <87v8grb7lx.fsf@toke.dk> (raw)
In-Reply-To: <92a90-421-da6-f85d-133727f3730@tarent.de>
Thorsten Glaser <t.glaser@tarent.de> writes:
> On Wed, 17 May 2023, Toke Høiland-Jørgensen wrote:
>
>>Well, if it's a custom qdisc you could just call skb_orphan() on the
>>skbs when enqueueing them?
>
> What does that even do? (Yes, I found the comment in skbuff.h that
> passes for documentation. It isn’t comprehensible to an aspiring
> qdisc writer though.)
It detaches the skb from the socket it came from; so from the TCP stack
PoV it will look like the packet left the machine, which should
short-circuit the backpressure thing...
-Toke
prev parent reply other threads:[~2023-05-17 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 12:54 knob to disable locally-originating qdisc optimisation? Thorsten Glaser
2023-04-27 20:21 ` Jakub Kicinski
2023-04-27 23:37 ` Stephen Hemminger
2023-05-16 16:38 ` Thorsten Glaser
2023-05-16 19:23 ` Toke Høiland-Jørgensen
2023-05-16 20:20 ` Thorsten Glaser
2023-05-16 22:11 ` Toke Høiland-Jørgensen
2023-05-16 23:01 ` Stephen Hemminger
2023-05-16 23:40 ` Thorsten Glaser
2023-05-16 23:44 ` Stephen Hemminger
2023-05-16 23:47 ` Thorsten Glaser
2023-05-17 3:02 ` Stephen Hemminger
2023-05-17 15:53 ` Thorsten Glaser
2023-05-16 23:41 ` Thorsten Glaser
2023-05-17 10:00 ` Toke Høiland-Jørgensen [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=87v8grb7lx.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Haye.Haehne@telekom.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=t.glaser@tarent.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.