Deutsch   English   Français   Italiano  
<vlerbj$16m4u$2@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Jerry Peters <jerry@example.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Are We Back to the "Wars" Now ?
Date: Sun, 5 Jan 2025 20:50:59 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <vlerbj$16m4u$2@dont-email.me>
References: <Sp-cnSz8UupYQaf6nZ2dnZfqnPednZ2d@earthlink.com> <vhmm4c$hnbj$1@dont-email.me> <vhmn2t$hv8i$3@dont-email.me> <vhnikj$me7m$1@dont-email.me> <vhoaau$qjkl$1@dont-email.me> <lIqcnTlkpf_Jtd36nZ2dnZfqn_udnZ2d@earthlink.com> <vhp9hs$12qaa$2@dont-email.me> <v4adnSK1nItcwNz6nZ2dnZfqnPWdnZ2d@earthlink.com> <vhrolu$1jata$1@dont-email.me> <Oo6dnZb3z-NT6Nz6nZ2dnZfqnPednZ2d@earthlink.com> <vhsdbi$1m6qu$1@dont-email.me> <vhth7o$1s5d5$4@dont-email.me> <heednZLHO-zE69_6nZ2dnZfqn_idnZ2d@earthlink.com> <vhvd06$2900d$1@dont-email.me> <vhvht1$28nn4$1@dont-email.me> <wwvldx8qw98.fsf@LkoBDZeT.terraraq.uk> <MTWdnX9Hd4WSXPb6nZ2dnZfqnPednZ2d@earthlink.com>
Injection-Date: Sun, 05 Jan 2025 21:51:00 +0100 (CET)
Injection-Info: dont-email.me; posting-host="43f233de20a7eb06ba01fe216ebe57ee";
	logging-data="1267870"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19MqYzHDsUzMpnl9Rh1TsGlWOiCN4wjQQw="
User-Agent: tin/2.4.5-20201224 ("Glen Albyn") (Linux/6.12.7 (x86_64))
Cancel-Lock: sha1:V8gXkQoOKUEYiwgdMk5mcFOyt+M=

186282@ud0s4.net <186283@ud0s4.net> wrote:
> On 11/24/24 2:14 PM, Richard Kettlewell wrote:
>> Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
>>> On Sun, 24 Nov 2024 14:25:10 +0000, Rich wrote:
>>>> 186282@ud0s4.net <186283@ud0s4.net> wrote:
>>>>> On 11/23/24 4:25 PM, Lawrence D'Oliveiro wrote:
>>>>>> That???s irrelevant.  Pipes originated on the earliest Unix machine,
>>>>>> which was a PDP-11 with only a 64kiB address space.  They work great
>>>>>> for pumping around gigabytes of data, but you don???t need
>>>>>> gigabyte-sized memory buffers to do that.
>>>>>
>>>>>    It all has to be SOMEWHERE ... if not in RAM then
>>>>>    on a mass storage device.
>>>>
>>>> Nope, at least not with pipes.
>>>
>>> Hold on a sec.... pipes are /buffered/ in RAM, so there's at least
>>> a small bit of ram set aside for each open pipe.
>> 
>> The word ???all??? isn???t just decoration.  The claim was ???it all has to be
>> somewhere???, and Rich???s point (as I understand it) is that it does not
>> all have to be somewhere.
>> 
>> For example,
>> 
>>    head -c $((1024*1024*1024)) /dev/urandom | sha256sum
>> 
>> puts a gigabyte of data through a pipe, but at no point does anything
>> allocate anywhere close to a gigabyte of storage of any kind.
> 
> 
>   There's truth here ... the gigabyte gets kinda 'spread out'.
> 
>   But what if it was ten GB, or 100 ?
> 
>   So, if you wanna count on sending vast quantities of
>   data in pipes, go ahead - it'll almost always work.
> 
>   Until vids go 16k or something ...
> 
>   As said LONG back ... each developer has to make
>   decisions based on their app and the 'likely'
>   systems/usage. There isn't really a 'wrong' or
>   'right' way here - just 'alternatives'. I like
>   terse pipes, you may not care.

You keep ignoring the piped-to program, it's running concurrently
(or with multiple cores, simultaneously) as long as it keeps reading
from the pipe the pipe will never fill up.