All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH iperf3 v3] add MPTCPv1 support
Date: Wed, 19 Jun 2024 10:37:25 +0200	[thread overview]
Message-ID: <47c423d7-e405-45a4-8398-cd999c6049bd@kernel.org> (raw)
In-Reply-To: <10ac1bd1eef26be7258aa6b67e4843d9c4f7ac88.camel@kernel.org>

Hi Geliang,

On 19/06/2024 03:52, Geliang Tang wrote:
> On Tue, 2024-03-12 at 16:14 +0800, Geliang Tang wrote:

(...)

>> Sorry, I open a new one before reading this:
>>
>> https://github.com/esnet/iperf/pull/1661
> 
> This pull request has not been merged yet, and I recently found that it
> has conflicted with other code, so I resolved the conflict and updated
> it this pull request again.

Thank you for having done that!

> In addition, I found that before my pull request, there was already a
> pull request for MPTCP support waiting
> (https://github.com/esnet/iperf/pull/1615 by "marcosfsch"). I guess it
> is because there are two conflicting requests with the same purpose
> that MPTCP support has not been merged. If this is the reason, can we
> contact "marcosfsch" to see if these two requests can be merged into
> one? It doesn't matter whether mine or his is merged.

I don't think that's the reason, but I just added a message on PR #1615.

> Or the reason why it has not been merged is that iperf maintainers are
> not interested in MPTCP support because he has not given us any
> feedback. If this is the case, it seems we have no choice but to give
> up supporting MPTCP in iperf.

Yes, that's a shame they didn't even provide any feedback... If they
don't want it, they should at least be clear about that. I just added a
message on your PR #1661, will see... Because I don't think we want to
maintain an MPTCP version on our side (who will use it apart from us?).

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2024-06-19  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  7:03 [PATCH iperf3 v3] add MPTCPv1 support Geliang Tang
2024-03-12  7:10 ` Matthieu Baerts
2024-03-12  7:27   ` Geliang Tang
2024-03-12  8:09     ` Matthieu Baerts
2024-03-12  8:14       ` Geliang Tang
2024-06-19  1:52         ` Geliang Tang
2024-06-19  8:37           ` Matthieu Baerts [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=47c423d7-e405-45a4-8398-cd999c6049bd@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    /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.