We just had our 41th meeting with Mat, Peter and Ossama (Intel OTC),
Christoph (Apple), Florian (Red Hat) and myself (Tessares).
Thanks again for this new good meeting!
Here are the minutes of the meeting:
new MPTCP design:
- New RFCv7:
* Added Florian's commits for kselftest/etc
* Fixed read length bug that Florian noted
* Fixed compilation without CONFIG_IPV6
* Fixed DSS re-parsing warning when reading partial skb
* ULP changes are not part of this patch-set (yet)
* note: what is on Gerrit is slightly different (sync with latest
- Reviews are welcomed!
- git fetch "https://github.com/multipath-tcp/mptcp_net-next"
refs/changes/74/446474/1 && git checkout FETCH_HEAD
Commits for upstream:
- do we need to add Reviewed-by/Acked-by/Signed-off-by?
- not for the moment
- in topic: only remove ChangeId ref
- in cover letter: we will see later how to mention that this
patch-set is supported by different people from different companies.
- now a few commits in "export" branch
- new 'for-review' branch:
- if you use TopGit internally to manage your different commits
you want to integrate on top of other MPTCP changes (on top of
t/upstream or export), you can now base your tree on top of 'for-review'
branch (you can also use it as target for 'git-review' or keep
't/upstream', that will be the same from a Gerrit point of view)
- this new branch 'for-review' is like 't/upstream' (top of the
tree) but without TopGit files: Gerrit will see when changes are
integrated in the tree (not like 'export') because Change-Id are
preserved and mark changes as merged automatically when it is in the
tree. Also with this new branch, you don't have any .top* files on this
- in other words:
- use this branch as base and target:
git checkout -b <new_feature> for-review
git commit -s
git review for-review
- note for Mat: for your existing patch-set: continue to use
't/upstream' as target not to create new changes. That's OK for Gerrit.
But you can rebase your patch-set on top of 'for-review'
- branches in our repo: →
- master → like mptcp_trunk but with less features. (still sync?)
- net-next → sync of Dave's net-next
- t/upstream → top of the tree containing our changes on top of
- t/* → other topic: correspond to one commit we want to send
upstream (.topdeps: parent topic(s) ; .topmsg: commit message)
- export → an export of the tree on top of net-next: what we
should send upstream
- for-review → same as t/upstream but without TopGit files: can
be use as a base and target for your reviews
Syzkaller for MPTCP running now on v0.94:
- Running on Christoph side
- really easy to setup
- would be nice to have it for MPTCP net-next
- good to restrict to net syscall
- for net-next, we just need to ask to create MPTCP socket
- MPTCP in syscall is already there!
- new patches will come!
Papers related to MPTCP:
- Fixed-Mobile Convergence in the 5G era: From Hybrid Access to
Converged Core → https://nms.kcl.ac.uk/toktam.mahmoodi/files/FMC-Network.pdf
- Florian will be there (and talk about Skb Meta Data Extensions
- Matthieu will be there (with 2 other colleagues)
- Peter will check if he can go
- Could be nice to meet each others at LPC 2019 (September 9-11,
- mptcp_v0.94 branch has been recently updated (sync with upstream)
- We propose to have the next one on Thursday, the 7th of March.
- Usual time: 17:00 UTC (9am PST, 6pm CET)
- Still open to everyone!
Feel free to comment on these points and propose new ones for the next
Talk to you next week,
Matthieu Baerts | R&D Engineer
Tessares SA | Hybrid Access Solutions
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium