linux-kernel - Re: threadlets as 'naive pool of threads', epoll, some measurements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070227103711.GD23170@2ka.mipt.ru>
Date:	Tue, 27 Feb 2007 13:37:12 +0300
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Davide Libenzi <davidel@...ilserver.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@....com.au>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ulrich Drepper <drepper@...hat.com>,
	Zach Brown <zach.brown@...cle.com>,
	"David S. Miller" <davem@...emloft.net>,
	Suparna Bhattacharya <suparna@...ibm.com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: threadlets as 'naive pool of threads', epoll, some measurements

On Tue, Feb 27, 2007 at 09:27:57AM +0100, Ingo Molnar (mingo@...e.hu) wrote:
> 
> * Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> 
> > > > Enough, you say micro-thread design is superior - ok, that is your 
> > > > point.
> > > 
> > > note that threadlets are not 'micro-threads'. A threadlet is more of 
> > > an 'optional thread' (as i mentioned it earlier): whenever it does 
> > > anything that makes it distinct from a plain function call, it's 
> > > converted into a separate thread by the kernel. Otherwise it behaves 
> > > like a plain function call and returns.
> > 
> > I know.
> > But it is rare case for the most situations, when things do not block, 
> > so I called it micro-thread, since it spawns a new thread (get from 
> > preallocated pool) for parallel processing.
> 
> ugh. Because 'it spawns a new thread from a preallocated pool' you are 
> arbitrarily renaming threadlets to 'micro-threads'?? The kernel could be 
> using a transparent thread pool for ordinary pthread recycling itself 
> (and will possibly do so in the future) - that does not make them a 
> micro-thread one iota. So please stop calling them micro-threads, 
> threadlets are a distinctly separate concept ...
> 
> ( And i guess you should know it perfectly well from my past mails in
>   this thread that i dont like micro-thread concepts at all, so are you
>   perhaps calling threadlets 'micro-threads' intentionally, just to 
>   force a predictably negative reaction from me? Maybe i should start 
>   renaming your code too and refer to kevents as 'kpoll'? That too makes
>   absolutely zero sense. This is getting really silly. )

I already think about renaming kevent aio, since it uses kaio name,
which you frequently reference too, but you definitely did not think
about kevent.

And out of curiosity, how masichistic I would look if I intentinally
want to receive negative reaction from you :)

As far as you can recall, in all syslet related threads I was always for
them, and definitely against micro-threads, but when we come to the land
of IO processing using event driven model - here I can not agree with
you.

So, ok, no micro-thread name.

> 	Ingo

-- 
	Evgeniy Polyakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/