From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-workers@math.gatech.edu
Subject: Re: more problems w/ irix
Date: Thu, 14 Nov 1996 11:05:35 -0500 [thread overview]
Message-ID: <199611141605.LAA15253@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Thu, 14 Nov 1996 15:38:43 GMT." <27656.199611141538@stone.dcs.warwick.ac.uk>
> >It doesn't exec a cat, it does the reading/writing itself (in closemn).
>
> I'm aware of that. I was responding to the statement that it is
> inefficient, saying that "foo <a <b <c" should be more efficient than
> "cat a b c | foo". If it isn't, we should make it so.
>
> >I'm not sure how we could make this more efficient without using something
> >like mmap().
>
> I think using mmap() would be a good move. An madvise(), as used by
> some cats, would also help performance. We can do autoconf checks for
> these functions, and would in any case need to have the code fall back
> on a read/write loop in case mmap() is impossible.
It's been a while since I looked at the source for something like
GNU cat, but I remember it being quite a bit of code (relative to
what it does). Also I believe it takes quite a bit of work to
write portable code that uses mmap().
I think of the multio as more of a convenience, rather than being
faster just because it is built into the shell. For scripting
purposes (where speed is more important), you can just use
"cat a b c | whatever".
I think it would be sufficient to just output an error message
such as "max multio's is 16", when someone tries
"whatever < *". They should use "cat * | whatever" instead.
We should probably mention this limit in the man pages.
rc
next prev parent reply other threads:[~1996-11-14 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-13 17:23 Ray Jones
1996-11-13 18:38 ` Bart Schaefer
1996-11-13 18:43 ` rjones
1996-11-14 10:01 ` Peter Stephenson
1996-11-14 15:08 ` Zefram
1996-11-14 15:23 ` Richard Coleman
1996-11-14 15:38 ` Zefram
1996-11-14 16:05 ` Richard Coleman [this message]
1996-11-15 11:09 ` Peter Stephenson
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=199611141605.LAA15253@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).