Re: [PATCH 01/45] Create a dynamically sized pool of threads for doing very slow work items [ver #41]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 21 Nov 2008 10:24:00 +0000 David Howells <dhowells@xxxxxxxxxx> wrote:

> Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> > umm, if they're slow, why not create a kernel thread per operation? 
> > Why add the thread pool?
> 
> Because if someone does a tar of, say, a kernel tree, that'll create one
> thread per file...

OK.

>  This provides a limiter - and makes sure there are threads
> immediately available.

Those two objectives seem incompatible.  What does a caller do when the
limit has been hit?  Do the work synchronously?

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux