From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: Weekly meeting - 25 June 2020 16:00 UTC (9am PDT, 6pm CEST)
Date: Thu, 02 Jul 2020 13:31:16 +0800 [thread overview]
Message-ID: <20200702053116.GA17066@OptiPlex> (raw)
In-Reply-To: eeeb860d-601d-6533-1578-3c997de842f0@tessares.net
[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]
Hi Matt,
On Wed, Jul 01, 2020 at 06:17:14PM +0200, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 26/06/2020 02:40, Geliang Tang wrote:
> > Hi Matt,
> >
> > There are several questions I didn't answer clearly in the last meeting.
> > Here I try to write them down:
>
> Thank you for the clarification!
>
> > 1 My name pronunciation
> > Geliang Tang sounds like Glenn Town.
>
> Thank you, that's helpful!
>
> > 2 My ideal meeting time
> > Every hour from 11am to 6pm (my location time-zone) at every working day
> > is fine to me to attend the meeting.
>
> I just sent another email now that I am back to work. Did you see it?
> I guess you subscribed to the ML but just in case: https://lists.01.org/hyperkitty/list/mptcp(a)lists.01.org/thread/SHULDCJUWQJX7CWUH6N66MFTRW6TAODS/
>
> The best would be to have a single meeting, once per week where everybody
> can join. But it would always be difficult for people of some time zones...
> I know it is very late and not in the working hours but do you think having
> the meeting one hour sooner (11pm your time) would be OK for you? Maybe not
> every week of course. Don't be afraid to say no!
>
11pm is fine to me. Hope it is not too early to other people.
-Geliang
> An alternative would be to organise other meetings with less people.
> But sadly, I don't see other possibilities. Feel free to share if any!
>
> > 3 What would you like to work on?
> > I'm interested in the BPF topic in the last meeting. But I don't have
> > any idea about this at the moment. Can you please give me more detail
> > about it and I'll spend some time to learn it.
>
> At the last meeting, we discussed about BPF because a new dev asked to work
> on this subject. He is for the moment looking at having the possibility to
> set in BPF some socket options per subflow.
>
> Maybe later, he might look at adding BPF_CGROUP_SOCKET to allow per-cgroup
> override of proto in the socket() call. More details in
> https://github.com/multipath-tcp/mptcp_net-next/issues/18
>
> But still in BPF, it would be good to look at other stuffs like modifying
> the behaviour of the Path Manager or the Scheduler with BPF.
> Some works were done in a fork of the out-of-tree kernel, maybe it can help:
> https://dial.uclouvain.be/pr/boreal/object/boreal:225610
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
next reply other threads:[~2020-07-02 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 5:31 Geliang Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-02 8:08 [MPTCP] Re: Weekly meeting - 25 June 2020 16:00 UTC (9am PDT, 6pm CEST) Matthieu Baerts
2020-07-01 16:17 Matthieu Baerts
2020-06-26 0:40 Geliang Tang
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=20200702053116.GA17066@OptiPlex \
--to=unknown@example.com \
/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.