From mboxrd@z Thu Jan  1 00:00:00 1970
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.ada
Subject: Re: In memory Stream
Date: Sun, 18 Feb 2024 00:02:33 -0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <uqrhep$lhl1$4@dont-email.me>
References: <uqnajr$svt$1@rasp.pasdenom.info>
	<uqqcpf$orp$1@rasp.pasdenom.info> <uqqfn4$eo0r$1@dont-email.me>
	<uqqgk6$oro$1@rasp.pasdenom.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 18 Feb 2024 00:02:33 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="ef266a3a922f269062f854d615e239ef";
	logging-data="706209"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/uN88IILpbIH7mffQIudTw"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:iuP3kd96G51Op0yN1xqD99I3EEk=
Xref: news.eternal-september.org comp.lang.ada:66084
List-Id: <comp.lang.ada>

On Sat, 17 Feb 2024 15:42:13 +0100, DrPi wrote:

> A memory buffer IS limited in size. It is either a peripheral buffer or
> a memory buffer you create yourself (my case). In either case, its size
> is limited. When writing in the stream, you have to care to not overflow
> the buffer.

With pipes, the OS takes care of this for you. Once its kernel buffer is 
full, further writes are automatically blocked until a reader has drained 
something from the buffer.

It’s called “flow control”.