From: Dominique Martinet <asmadeus@codewreck.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
ericvh@kernel.org, lucho@ionkov.net, andreas.noever@gmail.com,
YehezkelShB@gmail.com, corbet@lwn.net, linux-usb@vger.kernel.org,
v9fs@lists.linux.dev, linux-doc@vger.kernel.org,
linux_oss@crudebyte.com
Subject: Re: [PATCH 0/3] net/9p: Add 9P transport over USB4STREAM
Date: Tue, 10 Nov 2026 22:38:29 +0900 [thread overview]
Message-ID: <avMeVSDYT9p9PHz4@codewreck.org> (raw)
In-Reply-To: <20261109165236.GW176724@black.igk.intel.com>
Mika Westerberg wrote on Mon, Nov 09, 2026 at 05:52:36PM +0100:
> > In case of one-shot backup, I think my drag&drop scenario from cover-
> > letter fits it well. Assuming single thread copy, both transports
> > achieve similar results, but with busy-poll enabled, trans=thunderbolt
> > cuts about 1/3rd of copy time:
> > Copy from 9P client to a server, using trans=fd, takes 22m29s while
> > trans=thunderbolt + busy-poll takes 14m50s (~1.5x faster).
> > Reverse direction, same improvement: reducing copy time from 41m07s to
> > 26m56s. All done on default msize.
>
> That sounds like a good reason to include it IMHO. Also I like the
> simplicity - no need to run a separate descriptor feeding process :)
I'm sorry but I'm just not convinced it's useful enough to warrant the
effort to review this from my point of view given my lack of time for
linux work:
- most of the speed benefit comes from busy-poll, can't this be made to
work for all fd consumers somehow? (it could be an ioctl before passing
the fd to the mount call, or it could reuse e.g. the existing NAPI
config with network over usb4stream if that's more practical; in
particular I recall some drivers supporting a hybrid mode that'd
busy-poll for x ns/ms then fall back to waiting for the irq, that'd get
you the best of both worlds as a sane default)
- for simplicity it looks like mounting from boot without initrd isn't a
goal, so this can all be hidden in a userspace wrapper. 9p has
historically always been pretty bare, we're not even doing dns
resolution that has been a basic feature available for nfs since
forever.
You can look at this mount.9P helper for inspiration:
https://github.com/nfs-ganesha/nfs-ganesha/blob/V15.2/src/tools/mount.9P
> > I would be happy to maintain Thunderbolt transport.
>
> If Dominique is okay with this, I suggest to send v2 with a MAINTAINERS
> update as well.
OTOH if you're going to maintain this I have no reason to block, I can
just say I'm not reviewing in depth and pass the ball to Linus or
someone else higher up the stack to decide...
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2026-11-10 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:23 [PATCH 0/3] net/9p: Add 9P transport over USB4STREAM Alan Borzeszkowski
2026-09-24 16:23 ` [PATCH 1/3] thunderbolt: stream: Add tbstream_dev_from_file() Alan Borzeszkowski
2026-09-29 6:42 ` Mika Westerberg
2026-09-24 16:23 ` [PATCH 2/3] net/9p/thunderbolt: Add native 9P Thunderbolt transport support Alan Borzeszkowski
2026-09-24 16:23 ` [PATCH 3/3] Documentation/fs/9p: Add Thunderbolt transport documentation Alan Borzeszkowski
2026-10-29 2:45 ` [PATCH 0/3] net/9p: Add 9P transport over USB4STREAM Dominique Martinet
2026-11-02 15:39 ` Alan Borzeszkowski
2026-11-09 16:52 ` Mika Westerberg
2026-11-10 13:38 ` Dominique Martinet [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=avMeVSDYT9p9PHz4@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=YehezkelShB@gmail.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=corbet@lwn.net \
--cc=ericvh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=mika.westerberg@linux.intel.com \
--cc=v9fs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox