[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200205154829.wbgdp2r4gslnozpa@l29ah-x201.l29ah-x201>
Date: Wed, 5 Feb 2020 18:48:29 +0300
From: l29ah@...k.li
To: Dominique Martinet <asmadeus@...ewreck.org>
Cc: v9fs-developer@...ts.sourceforge.net,
Eric Van Hensbergen <ericvh@...il.com>,
Latchesar Ionkov <lucho@...kov.net>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] 9pnet: allow making incomplete read requests
On Wed, Feb 05, 2020 at 08:35:04AM +0100, Dominique Martinet wrote:
> Sergey Alirzaev wrote on Wed, Feb 05, 2020:
> > A user doesn't necessarily want to wait for all the requested data to
> > be available, since the waiting time is unbounded.
>
> 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.
--
() ascii ribbon campaign - against html mail
/\ http://arc.pasp.de/ - against proprietary attachments
Powered by blists - more mailing lists