From: Jeremy Jackson <jerj@coplanar.net>
To: netdev@vger.kernel.org
Subject: Re: querying TOS/DSCP at accept() time?
Date: Sun, 27 Dec 2009 11:05:05 -0500 [thread overview]
Message-ID: <1261929905.8193.24.camel@ragnarok> (raw)
In-Reply-To: <1261925852.8193.9.camel@ragnarok>
It seems this question was asked before in 2001:
http://www.squid-cache.org/mail-archive/squid-dev/200103/0035.html
http://lkml.indiana.edu/hypermail/linux/kernel/0103.0/1211.html
And apparently Squid developers made a kernel patch
http://zph.bratcheda.org/tos_marking_with_tos_preserving.htm
http://zph.bratcheda.org/
It seems like this is generally useful to a number of applications,
perhaps it should be included in mainstream kernel?
I see there's a structure member added, which will likely be frowned
upon, but perhaps it could be reworked to use the existing TOS byte
captured
net/ipv4/tcp_ipv4.c:1645
TCP_SKB_CB(skb)->flags = iph->tos;
Cheers,
Jeremy
The kernel patch adds
On Sun, 2009-12-27 at 09:57 -0500, Jeremy Jackson wrote:
> I would like to allow clients connecting to webserver to choose TOS/DSCP
> value they want in reply packets, based on TOS setting received by
> webserver in initial SYN-SYN/ACK-ACK exchange. Linux samples the TOS
> byte of the ACK that moves the state to CONNECTED, presumably to use for
> later ECN processing, but I cannot find a way to get this from
> userspace.
>
> net/ipv4/tcp_ipv4.c:1645
> TCP_SKB_CB(skb)->flags = iph->tos;
>
>
> Am I missing something in getsockopt(TCP_INFO perhaps?) or accept(), or
> is this currently not possible?
>
>
>
--
Jeremy Jackson
Coplanar Networks
(519)489-4903
http://www.coplanar.net
jerj@coplanar.net
prev parent reply other threads:[~2009-12-27 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 14:57 querying TOS/DSCP at accept() time? Jeremy Jackson
2009-12-27 16:05 ` Jeremy Jackson [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=1261929905.8193.24.camel@ragnarok \
--to=jerj@coplanar.net \
--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 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.