From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Kevin Hayes <kevinhayes@chromium.org>,
Kirtika Ruchandani <kirtika@google.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless workshop coming soon :-)
Date: Fri, 15 Mar 2019 14:06:29 +0100 [thread overview]
Message-ID: <87wol0walm.fsf@toke.dk> (raw)
In-Reply-To: <1d87a40795765be3ce9a485381c2867b143f26e1.camel@sipsolutions.net>
Johannes Berg <johannes@sipsolutions.net> writes:
> On Sun, 2019-03-10 at 20:21 -0700, Kevin Hayes wrote:
>> [resending after html mode got nacked..]
>>
>> Hi Johannes/Toke,
>> It would be fine with Kan and me to push the airtime fairness
>> discussion to later, to accomodate Toke.
>> Workshop fairness in action. :)
>
> :)
> Yes, I know we need to do that. Unfortunately I haven't had a chance to
> really build up a time-based agenda.
>
> Let's see. We have track 4 all day on Wednesday, overlaps are:
>
> | track 1 | track 2 | track 3
> 8:30 - 10:30 | TCP | XDP tut | IoT / U-LPWA
> 10:50 - 11:50 | TCP | Kubrnts | FRR
> 11:50 - 12:20 | netlink | QUIC | FRR dataplane
> 13:20 - 14:20 | netlink | QUIC | -
> 14:40 - 16:10 | TC | NF | -
> 16:30 - 18:00 | hw offl | preempt | -
>
> So the overlaps I know about are the XDP Tutorial (Toke) and netlink
> (partially at least, myself).
>
> Any others?
>
> Clearly Toke needs to be at the full XDP Tutorial, I think I can live
> with just doing the first part of the netlink workshop, according to
> their (tentative) agenda.
>
> As far as I'm concerned, we need Toke for the eBPF/XDP wifi topic, and
> clearly for all the topics related to TXQs, which includes at least part
> of HE/11ax. Toke, is there anything else you have a strong interest in?
>
>
> So tentatively, I'd say you can do w/o me for the FQ/airtime fairness
> stuff (right Toke, Kalle?) and talk about that at 11:50?
>
>
>
> Just randomly dropping the other stuff, I get:
>
> (T = no Toke, J = no Johannes)
>
> 8:30 - 9:00 T intro / CRDA deprecation / other regulatory topics?
> 9:00 - 9:30 T CSI reporting / vendor command/event handling updates
> 9:30 - 10:00 T nl80211 APIs - non-public features, NAN deprecation
> 10:00 - 10:30 T nl80211 APIs cont'd - Android
> 10:50 - 11:20 eBPF integration / XDP support for wifi
> 11:20 - 11:50 (buffer)
> 11:50 - 12:20 J rtw88 / grill Kalle (be)fore lunch ;-)
> 13:20 - 13:50 Kevin/Kan chromiumOS fairness review, bufferbloat plans
> 13:50 - 14:20 fq_codel / airtime fairness stack integration
> 14:40 - 15:10 HE/11ax status, timeline, testing, future work
> 15:10 - 15:40 HE/11ax TXQ AP-side (is anyone doing something here?)
> 15:40 - 16:10 release discussions (iw, wpa_s, ...)
> 16:30 - 17:00 security issue handling w/ backports
> 17:00 - 17:30 (buffer)
> 17:30 - 18:00
>
> WDYT?
SGTM :)
-Toke
next prev parent reply other threads:[~2019-03-15 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 10:49 wireless workshop coming soon :-) Johannes Berg
2019-03-01 11:11 ` Toke Høiland-Jørgensen
2019-03-01 11:12 ` Johannes Berg
2019-03-01 11:23 ` Toke Høiland-Jørgensen
2019-03-11 3:21 ` Kevin Hayes
2019-03-15 9:20 ` Johannes Berg
2019-03-15 9:21 ` Johannes Berg
2019-03-15 13:06 ` Toke Høiland-Jørgensen [this message]
2019-03-12 18:47 ` Kirtika Ruchandani
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=87wol0walm.fsf@toke.dk \
--to=toke@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=kevinhayes@chromium.org \
--cc=kirtika@google.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).