From: Kostis Kaffes <kkaffes@stanford.edu>
To: Xdp <xdp-newbies@vger.kernel.org>
Subject: KCM Multithreading Issue
Date: Sat, 1 May 2021 21:50:31 -0700 [thread overview]
Message-ID: <CAHAzn3pDuXPtE=S2PNgu_pdmDfY-tPjNZYMF8ZrvCs6GSRROxg@mail.gmail.com> (raw)
Hello,
I have been trying to use the Kernel Connection Multiplexor (KCM) for
request-level scheduling on top of TCP streams. The parent thread of a
multi-threaded server creates and clones KCM sockets. It then listens
for a pre-determined number of connections and attaches the connected
sockets to the first KCM socket it created. Finally, it spins up
threads that each uses one KCM socket to read() requests and write()
responses.
I observe that often the threads stop receiving, getting stuck in
read(), a couple of seconds after the program start. This behavior is
non-deterministic but it becomes more likely the more KCM sockets I
create.
Is there any known KCM bug or is this most likely an error from my side?
I apologize in advance if this is not the right channel for this question.
Best,
Kostis
reply other threads:[~2021-05-02 5:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAHAzn3pDuXPtE=S2PNgu_pdmDfY-tPjNZYMF8ZrvCs6GSRROxg@mail.gmail.com' \
--to=kkaffes@stanford.edu \
--cc=xdp-newbies@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).