Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030583AbWBHIui (ORCPT ); Wed, 8 Feb 2006 03:50:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030581AbWBHIui (ORCPT ); Wed, 8 Feb 2006 03:50:38 -0500 Received: from mx2.suse.de ([195.135.220.15]:3307 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1030583AbWBHIuh (ORCPT ); Wed, 8 Feb 2006 03:50:37 -0500 From: Andi Kleen To: Andrew Morton Subject: Re: [PATCH] add execute_in_process_context() API Date: Wed, 8 Feb 2006 09:50:11 +0100 User-Agent: KMail/1.8.2 Cc: James.Bottomley@steeleye.com, linux-kernel@vger.kernel.org References: <1139342419.6065.8.camel@mulgrave.il.steeleye.com.suse.lists.linux.kernel> <20060208001833.49300fe1.akpm@osdl.org> In-Reply-To: <20060208001833.49300fe1.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602080950.11606.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 814 Lines: 23 On Wednesday 08 February 2006 09:18, Andrew Morton wrote: > Andi Kleen wrote: > > > > James Bottomley writes: > > > > In general this seems like a lot of code for a simple problem. > > It might be simpler to just put the work structure into the parent > > object and do the workqueue unconditionally > > > > That apparently would have really bad performance problems. If we're > !in_interrupt() we want to do the work synchronously. It depends if it's common or not. If it's uncommon then simpler code is better. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/