From: "Toke Høiland-Jørgensen" <toke@redhat•com>
To: "Tyler Wear" <twear@quicinc•com>,
"Martin KaFai Lau" <kafai@fb•com>,
"Maciej Żenczykowski" <maze@google•com>
Cc: "Tyler Wear (QUIC)" <quic_twear@quicinc•com>,
Yonghong Song <yhs@fb•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"bpf@vger•kernel.org" <bpf@vger•kernel.org>
Subject: RE: [PATCH] Bpf Helper Function BPF_FUNC_skb_change_dsfield
Date: Mon, 03 Jan 2022 21:59:00 +0100 [thread overview]
Message-ID: <87a6gccz8r.fsf@toke.dk> (raw)
In-Reply-To: <BYAPR02MB52382D9342669D4D578C85D8AA7C9@BYAPR02MB5238.namprd02.prod.outlook.com>
Tyler Wear <twear@quicinc•com> writes:
>> On Tue, Dec 21, 2021 at 02:13:04PM -0800, Maciej Żenczykowski wrote:
>> > > > As for what is driving this? Upcoming wifi standard to allow
>> > > > access points to inform client devices how to dscp mark individual flows.
>> > > Interesting.
>> > >
>> > > How does the sending host get this dscp value from wifi and then
>> > > affect the dscp of a particular flow? Is the dscp going to be
>> > > stored in a bpf map for the bpf prog to use?
>> >
>> > It gets it out of band via some wifi signaling mechanism.
>> > Tyler probably knows the details.
>> >
>> > Storing flow match information to dscp mapping in a bpf map is indeed the plan.
>> >
>
> This is for an upcoming QoS Wifi Alliance spec.
Got a link, or some other information about the specifics of this? :)
-Toke
prev parent reply other threads:[~2022-01-03 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 20:40 [PATCH] Bpf Helper Function BPF_FUNC_skb_change_dsfield Tyler Wear
2021-12-21 3:18 ` Yonghong Song
2021-12-21 6:16 ` Martin KaFai Lau
2021-12-21 19:16 ` Tyler Wear (QUIC)
2021-12-21 19:46 ` Maciej Żenczykowski
2021-12-21 21:52 ` Martin KaFai Lau
2021-12-21 22:13 ` Maciej Żenczykowski
2021-12-21 23:07 ` Martin KaFai Lau
2021-12-21 23:28 ` Tyler Wear
2022-01-03 20:59 ` 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=87a6gccz8r.fsf@toke.dk \
--to=toke@redhat$(echo .)com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=kafai@fb$(echo .)com \
--cc=maze@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=quic_twear@quicinc$(echo .)com \
--cc=twear@quicinc$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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