Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc
Subject: Re: Python (was Re: I did not inhale)
Date: Tue, 20 Aug 2024 08:57:07 +0200
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <va1eo4$39jpi$1@dont-email.me>
References: <uu54la$3su5b$6@dont-email.me> <20240408075547.000061e8@gmail.com>
 <g52cnWOOwoz_son7nZ2dnZfqnPWdnZ2d@brightview.co.uk>
 <uvbe3m$2cun7$1@dont-email.me> <uvbfii$3mom0$1@news.xmission.com>
 <20240412094809.811@kylheku.com> <87il0mm94y.fsf@tudado.org>
 <way-20240413091747@ram.dialup.fu-berlin.de> <87il0lldf8.fsf@tudado.org>
 <choices-20240413123957@ram.dialup.fu-berlin.de>
 <v9lm2k$12qhv$1@dont-email.me> <v9m4gd$14scu$1@dont-email.me>
 <20240815182717.189@kylheku.com> <v9npls$1fjus$1@dont-email.me>
 <v9posc$1rpdj$1@dont-email.me> <v9pvoo$1sn55$1@dont-email.me>
 <v9r60h$2289h$2@dont-email.me> <v9sa91$2afht$1@dont-email.me>
 <v9tv8o$2iahp$1@dont-email.me> <v9uso3$2pdrg$2@dont-email.me>
 <v9v0n6$2q8h3$1@dont-email.me> <v9v8pr$2r6q2$2@dont-email.me>
 <va0j0i$3267t$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 20 Aug 2024 08:57:09 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="3d89229229cc5613f9a4092209d4175c";
	logging-data="3460914"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+VrznNdr+5ubwkoMyXPwoMe5/iJj71Okk="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:91K/so34ISDxU1GJtBi0tJU1tkI=
Content-Language: en-US
In-Reply-To: <va0j0i$3267t$1@dont-email.me>
Bytes: 2559

On 2024-08-20 01:03, Lawrence D'Oliveiro wrote:
> On Mon, 19 Aug 2024 13:03:23 +0200, Dmitry A. Kazakov wrote:
> 
>> Again. It is called overlapped I/O. You can start multiple
>> *asynchronous* I/O operations from a thread.
> 
> I’m not talking about using threads. I’m talking about avoiding threads,
> and all their potential for difficult-to-fix race-condition-type bugs.
> 
> I’m talking about situations where the bottleneck is the I/O, not the CPU,
> so multithreading gets you nothing.

It seems you suffer some form of dyslexia. I clearly stated that all 
instances of overlapped I/O is started from the same/single/one thread. 
Better now?

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de