Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 18725 invoked by uid 500); 14 Jul 2001 19:03:37 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 18705 invoked from network); 14 Jul 2001 19:03:35 -0000 From: "Sander Striker" To: Cc: Subject: Terminiting threads in a process RE: [PATCH] Problems with MPM threaded Date: Sat, 14 Jul 2001 21:13:08 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N >> By having the possibility of having other children processes, you now >> need a mechanism to kill all threads in the same process efficiently. >> You'd need to kick them out of the accept mutex, but I'm not seeing >> how that's going to happen quickly. -- justin > > You need to be able to kill all threads in a process efficiently > regardless. We will always need to be able to re-spawn processes that > die, and we will always have the concept of MaxRequestsPerChild. If a > process is going to die and be replaced, then we need to kill all the > threads in that process as quickly as possible. Only allowing one > process at a time doesn't remove that requirement. The way I see it, each process has a single pool instance as the parent for all the threads. Resetting or destroying that pool should effectively kill all threads. What am I missing? Sander