Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > comp.os.linux.misc > #62613

Re: Are We Back to the "Wars" Now ?

Show all headers | View raw

On 2024-12-18, Rich <rich@example.invalid> wrote:
> 186282@ud0s4.net <186283@ud0s4.net> wrote:
>> On 12/17/24 8:23 PM, Lawrence D'Oliveiro wrote:
>>> On Tue, 17 Dec 2024 13:34:30 +0000, Geoff Clare wrote:
>>> 
>>>> With a pipe or FIFO, you just use simple read and write operations 
>>>> and the system handles all the messy stuff for you.  If the pipe 
>>>> reaches capacity, write blocks until there is room to write some 
>>>> more; if the pipe becomes empty, read blocks until there is more 
>>>> data available; when read returns EOF that's the end of the data.
>>> 
>>> Yup. Furthermore:
>>> 
>>> * When the last writer closes its end, any remaining read attempts 
>>> get EOF.
>>> * When the last reader closes its end, any remaining write attempts 
>>> get “broken pipe”.
>> 
>>   But you're still limited to the amount of RAM the system can 
>>   access.
>
> Not with a pipe or FIFO, which is what is being discussed above.
>
> The amount of data you can transfer over a pipe is not in any way 
> limited by system memory size or any other system imposed limits.
>
>>   These days that's probably a LOT - but might NOT be,
>>   esp for 'embedded' type boards like the older PIs,
>>   BBBs and such. Never assume the user has essentially
>>   infinite RAM.
>
> The system will not have infinite RAM.  You can transfer infinite data 
> over a pipe (although it will take a while to reach infinity).

A pipe is _NOT_ limited to system RAM!

Using a named pipe on a Raspberry Pi model 1 with a _half_ GB of
total RAM, I would routinely transfer _several_ GB in a single
stream from an mplayer process to a netcat process.  The only
reason that's not currently happening every night these days is
the amplified TV antenna lost too much gain due to age, attic
heat, etc.

HTH

-- 
Robert Riches
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: Are We Back to the "Wars" Now ? rlhamil@smart.net (Richard L. Hamilton) - 2024-12-14 08:06 +0000
  Re: Are We Back to the "Wars" Now ? Pancho <Pancho.Jones@proton.me> - 2024-12-14 10:10 +0000
    Re: Are We Back to the "Wars" Now ? root <NoEMail@home.org> - 2024-12-14 15:54 +0000
      Re: Are We Back to the "Wars" Now ? The Natural Philosopher <tnp@invalid.invalid> - 2024-12-14 16:06 +0000
        Re: Are We Back to the "Wars" Now ? Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2024-12-17 13:34 +0000
          Re: Are We Back to the "Wars" Now ? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-18 01:23 +0000
            Re: Are We Back to the "Wars" Now ? "186282@ud0s4.net" <186283@ud0s4.net> - 2024-12-17 23:25 -0500
              Re: Are We Back to the "Wars" Now ? Rich <rich@example.invalid> - 2024-12-18 05:01 +0000
                Re: Are We Back to the "Wars" Now ? Robert Riches <spamtrap42@jacob21819.net> - 2024-12-18 05:12 +0000
                Re: Are We Back to the "Wars" Now ? Rich <rich@example.invalid> - 2024-12-18 14:03 +0000
                Re: Are We Back to the "Wars" Now ? Robert Riches <spamtrap42@jacob21819.net> - 2024-12-19 04:27 +0000
                Re: Are We Back to the "Wars" Now ? Rich <rich@example.invalid> - 2024-12-19 14:07 +0000
                Re: Are We Back to the "Wars" Now ? D <nospam@example.net> - 2024-12-19 16:02 +0100
                Re: Are We Back to the "Wars" Now ? Richard Kettlewell <invalid@invalid.invalid> - 2024-12-18 08:27 +0000
                Re: Are We Back to the "Wars" Now ? Rich <rich@example.invalid> - 2024-12-18 14:02 +0000
                Re: Are We Back to the "Wars" Now ? John Ames <commodorejohn@gmail.com> - 2024-12-18 08:11 -0800
                Re: Are We Back to the "Wars" Now ? Rich <rich@example.invalid> - 2024-12-18 16:51 +0000
                Re: Are We Back to the "Wars" Now ? Richard Kettlewell <invalid@invalid.invalid> - 2024-12-18 18:32 +0000

csiph-web