From: Andi Kleen <andi@firstfloor.org>
To: "David Täht" <dave.taht@gmail.com>
Cc: netdev@vger.kernel.org, bloat-devel@lists.bufferbloat.net
Subject: Re: Asserting ECN from userspace?
Date: Thu, 06 Oct 2011 16:52:05 -0700 [thread overview]
Message-ID: <m2hb3l3cgq.fsf@firstfloor.org> (raw)
In-Reply-To: <4E8BF6B2.6030101@gmail.com> ("David =?utf-8?Q?T=C3=A4ht=22's?= message of "Tue, 04 Oct 2011 23:18:26 -0700")
David Täht <dave.taht@gmail.com> writes:
>
> And twiddling them, on a per stream basis, for a single packet, would
> seem to require something more robust than setsockopt/getsockopt
> (although that would work for udp streams)
With netfilter nf_queue you can construct a rule that passes packets
through user space and reinjects them.
I would suggest to just use that to modify the ECN bits.
I'm sure with reasonable google skills you can find some examples
how to do this on the web.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2011-10-06 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 6:18 David Täht
2011-10-06 23:52 ` Andi Kleen [this message]
2011-10-07 5:23 ` Eric Dumazet
2011-10-07 17:25 ` Rick Jones
2011-10-13 11:30 ` Juliusz Chroboczek
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=m2hb3l3cgq.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
/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