All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rao Shoaib <rao.shoaib at oracle.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [Weekly meetings] MoM - 16th of April 2018
Date: Mon, 23 Apr 2018 13:13:41 -0700	[thread overview]
Message-ID: <9bd1a123-b4fb-00d4-0cc9-1200cbb71bc5@oracle.com> (raw)
In-Reply-To: 021c8818-f78d-5e02-9a76-aaa715ac39c8@tessares.net

[-- Attachment #1: Type: text/plain, Size: 4083 bytes --]

Hi Matthieu,

For the next meeting on the 26th can you add discussion of Oracle's patch.

Thanks,

Shoaib


On 04/16/2018 10:18 AM, Matthieu Baerts wrote:
> Hello,
>
> We just had our 6th meeting with Mat (Intel OTC), Christoph (Apple) 
> and myself (Tessares).
>
> Thanks again for this new good meeting!
>
> Please note that this meeting was exceptionally on Monday because it 
> was not possible to have it at the end of last week nor at the end of 
> this week. We propose to have the next meeting next Thursday (26th of 
> April). Feel free to propose other dates if needed.
>
>
>
> Here are the minutes of the meeting:
>
>
>
> Progress from last week:
>     - as expected, many people off or busy with other stuffs, not so 
> much new to share.
>     - Mat has updated the mptcp_net-net repo (see below)
>     - Mat is dealing with issue on the client side (version from 
> github.com/multipath-tcp/mptcp) when using it with a modified server 
> (having his patches). More discussions will continue later with a pcap.
>     - Matthieu finished the review of Christoph's patches (Note for 
> myself: not the review of Christoph's Paasch, that's different...). Do 
> not hesitate to review the two last commits.
>
>
>
> mptcp_net-next merge:
>     - Mat started the work: 
> https://github.com/multipath-tcp/mptcp_net-next/
>     - one fix has been done (related to checksum and gso), seems OK, 
> feel free to comment if not: 
> https://github.com/multipath-tcp/mptcp_net-next/commit/6ba7f217d3a69a88152a3fbee8b9dfc47c77bf4d
>     - Christoph will try to launch some tests using this branch
>     - Could be good to merge with net-next once per week to reduce the 
> amount of conflicts we need to fix in once
>     - Could be good to have two branches:
>         - one close to net-next and the current mptcp_trunk
>         - one where we have a minimal implementation → focus on the 
> client, simple version.
>
>
>
> netdevconf:
>     - tutorial ideas: more should come. Feel free to propose any idea.
>     - Matthieu is trying to get more ideas
>     - Matthieu: will start a dedicated discussion on the ML (should do 
> that on Wednesday (or short after) after having collected more ideas)
>
>
>
> topgit to manage patch sets, maybe not needed now, maybe later
>     - looks like a good tool for what we have to do
>     - could be good to have a look:
>         https://github.com/mackyle/topgit (new version -- recommended)
>         https://github.com/greenrd/topgit (original version)
>     - Matthieu has some experiences with it if you need some support.
>     - Feel free to try it, instructions are in the README
>
>
>
> LPC:
>     - From Mat: still not clear what it will be.
>     - it is possible that they will have more miniconferences and they 
> will prefer that
>     - but will be a lot of people there (davem), very interesting to 
> participate, get feedback, help, advises, etc.
>     - the networking track submission deadline for LPC is July 11: 
> http://vger.kernel.org/lpc-networking.html → 350 word proposal for a 
> 40 minute talk plus 2-10 page paper.
>
>
>
> Next steps:
>     - Mat: wiki update: with links, etc. (could be good, when the base 
> is there, to have some help to maintain that, at least reporting 
> outdated links, etc.
>     - Christoph: will first look at the lockless patches then maybe 
> look at the net-next branch
>     - Peter will also look at mptcp-net-next branch + continue to work 
> on the patch-set with Mat
>     - Matthieu: update Netlink PM patches.
>
>
>
> Next meeting:
>     - proposition: the 26th of April at 9am PDT - 16:00 UTC (9am PDT, 
> 6pm CEST)
>     - open to everyone!
>     - https://annuel2.framapad.org/p/mptcp_upstreaming_20180426
>
>
>
> Feel free to comment these points and propose new ones for the next 
> meeting!
>
>
>
> Talk to you next week,
> Matthieu


             reply	other threads:[~2018-04-23 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 20:13 Rao Shoaib [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-30 18:35 [MPTCP] [Weekly meetings] MoM - 16th of April 2018 Rao Shoaib
2018-04-30 16:34 Christoph Paasch
2018-04-27  0:43 Rao Shoaib
2018-04-26 22:20 Christoph Paasch
2018-04-26 21:25 Rao Shoaib
2018-04-26 20:52 Christoph Paasch
2018-04-26 19:04 Rao Shoaib
2018-04-26 18:31 Rao Shoaib
2018-04-26 17:27 Matthieu Baerts
2018-04-24 10:46 Matthieu Baerts
2018-04-16 17:18 Matthieu Baerts

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=9bd1a123-b4fb-00d4-0cc9-1200cbb71bc5@oracle.com \
    --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.