From: Dominique Martinet <asmadeus@codewreck.org>
To: l29ah@cock.li
Cc: v9fs-developer@lists.sourceforge.net,
Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] 9pnet: allow making incomplete read requests
Date: Wed, 5 Feb 2020 17:07:29 +0100 [thread overview]
Message-ID: <20200205160729.GA10862@nautica> (raw)
In-Reply-To: <20200205154829.wbgdp2r4gslnozpa@l29ah-x201.l29ah-x201>
l29ah@cock.li wrote on Wed, Feb 05, 2020:
> On Wed, Feb 05, 2020 at 08:35:04AM +0100, Dominique Martinet wrote:
> > I'm not sure I agree on the argument there: the waiting time is
> > unbounded for a single request as well. What's your use case?
>
> I want to interface with synthetic file systems that represent
> arbitrary data streams.
> The one where i've hit the problem is reading the log of a XMPP chat
> client that blocks if there's no new data available.
Definitely a valid use case for 9p, please rephrase your commit message
to describe the problem a bit better.
I'll wait for a v2 removing the 'total' variable from
p9_client_read_once anyway, unless you disagree.
Thanks,
--
Dominique
prev parent reply other threads:[~2020-02-05 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 0:34 [PATCH 1/2] 9pnet: allow making incomplete read requests Sergey Alirzaev
2020-02-05 0:34 ` [PATCH 2/2] 9p: read only once on O_NONBLOCK Sergey Alirzaev
2020-02-05 7:41 ` Dominique Martinet
2020-02-05 7:35 ` [PATCH 1/2] 9pnet: allow making incomplete read requests Dominique Martinet
2020-02-05 15:48 ` l29ah
2020-02-05 16:07 ` 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=20200205160729.GA10862@nautica \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=l29ah@cock.li \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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