Received: by 10.223.148.5 with SMTP id 5csp6919929wrq; Wed, 17 Jan 2018 21:44:44 -0800 (PST) X-Google-Smtp-Source: ACJfBot3bhLqUEAdXx/nJA0QhVZtMlxE4yXv//MfSYy5jikiMTjQbB0RgMCiYLtP7gOBgHqQzHzO X-Received: by 10.98.7.73 with SMTP id b70mr13081040pfd.39.1516254284007; Wed, 17 Jan 2018 21:44:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516254283; cv=none; d=google.com; s=arc-20160816; b=RM8Q76Fz5F68LGEpMfwXZlMD2+N6Poj3N5VCC0eKoGqZAM0DAiX8ZhJzAbB1j6ZGDp Z+agUuceJVJDlunGI6tbKOQN964vfCsCa+Wr1+iSxYV7WVWezw8LmDWE4XBGcf74Ytkp Bqf1q/h3n8eJhZgRDbwFlIRrychvLNdA2mkQPcnC7aVfEKGQZaJSod1K8W5SBhB4r94F WtGrP8vTmv/dVOj84kf7TV42fep0sW//FcPoZ0RTZpkFrvhVOhEyVV8F/sUCYqqG93bd m+jMrhIyKazVVqJOa/PtrJFLGemCBIqS/qHfsdaZ9XfvxsNxY01XVO6iem1668MX9DF5 nwGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=z9YiIAYsQDE+99cNRldFkrxxb1JhZpoL7N/BgFwu0vw=; b=0KAEnPIi3Ig6qOmJe/gk1NCZ1u1Zqw17PExJRtbrf2hKC66jboSnzxGpQmK8aDU/fe wanxpn4w7hTU73Gt4sc2WSUlRanB2Br7ixsIqOuoexZscRh33ik/EdCdwUCYAulE7sPi PsnJEiGKWA56BvJAuhQ2e9kzx4tLpvsPY6Te3pX3aH8r4/ff5LfNA1ay1Gp8MmIWnpx4 af9c9Iloz5IaC2/z92GU13aJZXWBIW0dBpkLrA/Te6XoyvtxRPddlREZW9ybLDM8tuyq +jVJdYhfY6YYVM2Xguu3o0J+BvdgPeIdgCvZrli/Umn/I0ahSVqXl5Tus/BX5qTY51GU cX1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RKA0Z5W9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n1si5872731pld.395.2018.01.17.21.44.30; Wed, 17 Jan 2018 21:44:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RKA0Z5W9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754601AbeARFn6 (ORCPT + 99 others); Thu, 18 Jan 2018 00:43:58 -0500 Received: from mail-pg0-f47.google.com ([74.125.83.47]:45676 "EHLO mail-pg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754094AbeARFn5 (ORCPT ); Thu, 18 Jan 2018 00:43:57 -0500 Received: by mail-pg0-f47.google.com with SMTP id c194so13141871pga.12 for ; Wed, 17 Jan 2018 21:43:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=z9YiIAYsQDE+99cNRldFkrxxb1JhZpoL7N/BgFwu0vw=; b=RKA0Z5W9pJ7enAztp64yeoC+iQHI7MIAEygiXyME9+/uDjNjQNTZu8aCINa++BWUbL OcxoJaA0TQ9HEHPL9Sukkq+nGAcRqQ+Jvmugq5njjsJo479CEqzO5IijavY2oL4nfSVZ q9rXmHPf90MO1+ymcOyAPnuxMEfU6AjezOPu8vh6IF41qO2Aw0obSz58yinDH4cbeyny cWMbMh+xw97mb5DMestlep8g48ppfBcfP/OWW3vB85poirWaPSFTbcMm2J9tN/f0kMhr 6tqgLIYGl1/IO/Najn6EoBre3Nit2Nv1vwW/eTaHVWaLC1IdZynrN7D356IjXpasjJin /MVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=z9YiIAYsQDE+99cNRldFkrxxb1JhZpoL7N/BgFwu0vw=; b=jXW9Mf/bmuF4SnMRQrSqhgscdSc+szbseE5EFJffUToJbQJjsEsfpQv8gc6v7nHKym UkZGDH2WSqELze+VV+Vqs/ukAWxptKzW7OOrgo6K9Chg6E6YDhHEn/9DumpHYEi48df9 vBsXKZaJuUuTgVrQ1+SZegriSIJvqorwkIJtEoFqpGX9RJlV7yCVgLNyRJvLnG3wbX0Y 53rK3kOPcHG+DNiOE7I+ucBY3Kx5XTZdTFPVCwPCHIy3HF5wM6TUA5C3WnEsthpIkrBR Ljmy/FSRI9LgfkZJOfflhx3oCLJyXRFQt7zjbHoVmrY6QV2a4E0XMe3NSu+Ua0KtkRfB mn1w== X-Gm-Message-State: AKGB3mJbBMANwYWx+pKa5qlSKnbqDs8ev6E4hUO3EKxBq2XTtU04OKQ0 AOcEphagXw8XeWwn+tpZsYg= X-Received: by 10.98.192.10 with SMTP id x10mr32249866pff.27.1516254236900; Wed, 17 Jan 2018 21:43:56 -0800 (PST) Received: from localhost ([175.223.17.239]) by smtp.gmail.com with ESMTPSA id v24sm10525126pgc.82.2018.01.17.21.43.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 17 Jan 2018 21:43:55 -0800 (PST) Date: Thu, 18 Jan 2018 14:43:52 +0900 From: Sergey Senozhatsky To: Tejun Heo Cc: Steven Rostedt , Petr Mladek , Sergey Senozhatsky , Sergey Senozhatsky , akpm@linux-foundation.org, linux-mm@kvack.org, Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Linus Torvalds , Jan Kara , Mathieu Desnoyers , Tetsuo Handa , rostedt@home.goodmis.org, Byungchul Park , Pavel Machek , linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup Message-ID: <20180118054352.GC6529@jagdpanzerIV> References: <20180111093435.GA24497@linux.suse> <20180111103845.GB477@jagdpanzerIV> <20180111112908.50de440a@vmware.local.home> <20180111203057.5b1a8f8f@gandalf.local.home> <20180111215547.2f66a23a@gandalf.local.home> <20180116194456.GS3460072@devbig577.frc2.facebook.com> <20180117091208.ezvuhumnsarz5thh@pathway.suse.cz> <20180117151509.GT3460072@devbig577.frc2.facebook.com> <20180117121251.7283a56e@gandalf.local.home> <20180117200551.GW3460072@devbig577.frc2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180117200551.GW3460072@devbig577.frc2.facebook.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (01/17/18 12:05), Tejun Heo wrote: [..] > > This could very well be a great place to force offloading. If a printk > > is called from within a printk, at the same context (normal, softirq, > > irq or NMI), then we should trigger the offloading. > > I was thinking more of a timeout based approach (ie. if stuck for > longer than X or X messages, offload) yep, that's what I want. for a whole bunch of different reasons. -ss