From: Giacomo Tesio <giacomo@tesio.it>
To: 9front@9front.org
Subject: Re: [9front] bio io functions
Date: Thu, 4 May 2017 19:52:14 +0200 [thread overview]
Message-ID: <CAHL7psHNgxD7y78yX46OqspbWoPo7w61aGc_M2tw9x6XmPGVzA@mail.gmail.com> (raw)
In-Reply-To: <CAAsuYKcoU1560um002U_wmRFm0fq0iEf+b1bET7RQCTWqbHXrg@mail.gmail.com>
Nice idea. What do you have in mind instead of file descriptor?
What about returning the current function from Biofn to allow filters'
composition?
Giacomo
2017-05-04 18:23 GMT+02:00 Benjamin Purcell <benjapurcell@gmail.com>:
> I love it
>
> spew
>
> On Thu, May 4, 2017 at 11:02 AM, Julius Schmidt <aiju@phicode.de> wrote:
>> I would like to change bio to do all I/O through a user replaceable
>> function. The attached patch does just that, adding a new function Biofn()
>> to register such a function, which replaces read/write.
>>
>> Main uses I have in mind:
>>
>> 1. Allow programs to flush output buffers before stalling for more input,
>> which would most likely be activated with a command line flag.
>>
>> 2. Use bio with things that are not file descriptors.
>>
>> 3. Apply filters to input/outputs (arguably could also be done with pipes).
>>
>> 4. Use bio with ioprocs.
next prev parent reply other threads:[~2017-05-04 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 16:02 Julius Schmidt
2017-05-04 16:23 ` [9front] " Benjamin Purcell
2017-05-04 17:52 ` Giacomo Tesio [this message]
2017-05-04 20:18 ` Bruce Ellis
2017-05-04 20:21 ` Benjamin Purcell
2017-05-05 9:11 ` hiro
2017-05-05 9:14 ` Bruce Ellis
2017-05-05 9:55 ` Julius Schmidt
2017-05-05 9:56 ` Bruce Ellis
2017-05-05 10:21 ` Stanley Lieber
2017-05-05 10:29 ` Bruce Ellis
2017-05-05 10:32 ` Stanley Lieber
2017-05-05 10:33 ` Bruce Ellis
2017-05-05 11:05 ` Stanley Lieber
2017-05-05 12:11 ` hiro
2017-05-05 15:24 ` Kurt H Maier
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=CAHL7psHNgxD7y78yX46OqspbWoPo7w61aGc_M2tw9x6XmPGVzA@mail.gmail.com \
--to=giacomo@tesio.it \
--cc=9front@9front.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 NNTP newsgroup(s).