From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752230AbcGBLeH (ORCPT ); Sat, 2 Jul 2016 07:34:07 -0400 Received: from mail-oi0-f47.google.com ([209.85.218.47]:33345 "EHLO mail-oi0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752159AbcGBLeE (ORCPT ); Sat, 2 Jul 2016 07:34:04 -0400 Date: Sat, 2 Jul 2016 06:34:01 -0500 From: Tejun Heo To: Bhaktipriya Shridhar Cc: Tomi Valkeinen , Jean-Christophe Plagniol-Villard , Oleg Nesterov , Andrew Morton , linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] omapfb: omapfb-main: Remove deprecated create_singlethread_workqueue Message-ID: <20160702113401.GD17431@htj.duckdns.org> References: <20160702083056.GA26936@Karyakshetra> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160702083056.GA26936@Karyakshetra> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 02, 2016 at 02:00:56PM +0530, Bhaktipriya Shridhar wrote: > The workqueue auto_update_work is involved in auto updating mode for > manual-update displays. omapfb driver uses a delayed work item to update > the display at a constant rate. > > Since these long-running work items aren't involved in memory reclaim in > any way, system_long_wq has been used. Can you please explain why this is long-running? Thanks. -- tejun