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]

 



Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

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

No.  The work is queued for later processing by the pool.  The piece of memory
that records the pending work is much smaller than the memory required to hold
a thread.  The threads in the pool actually do the work.  The submitter of the
work gets on with its life - unless it has to be synchronous.

David
--
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