From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next] mptcp: use mptcp worker for path management
Date: Mon, 22 Jun 2020 15:03:10 +0200 [thread overview]
Message-ID: <20200622130310.GQ26990@breakpoint.cc> (raw)
In-Reply-To: 3274892c9713c52432c0e06d1b66a0a5028c9ec1.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> On Mon, 2020-06-22 at 13:18 +0200, Florian Westphal wrote:
> > Paolo Abeni <pabeni(a)redhat.com> wrote:
> > > I'm wondering if we should keep using an MPTCP-specific workqueue.
> > > Server side, we don't expect the work to trigger very often, but should
> > > that ever happen, top will tell easily.
> >
> > You mean switch msk->work from system_wq to a custom workqueue?
>
> yep, e.g. reusing and renaming 'pm_wq'. When the PM works a lot (in
> "ndiffports" mode as in issues/33), the pm_wq is visible in top - at
> least in dbg build, I never tested with regular kconfig - and I like
> being able to identify it easily. WDYT?
Can you do this?
I am not at all sure how you would like this to look like 8-(
(Merge parts of protocol.c into pm.c?)
next reply other threads:[~2020-06-22 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 13:03 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-24 16:29 [MPTCP] Re: [PATCH mptcp-next] mptcp: use mptcp worker for path management Matthieu Baerts
2020-06-22 14:51 Paolo Abeni
2020-06-22 11:30 Paolo Abeni
2020-06-22 11:18 Florian Westphal
2020-06-19 14:27 Paolo Abeni
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=20200622130310.GQ26990@breakpoint.cc \
--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.