Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3198308imu; Mon, 28 Jan 2019 00:06:06 -0800 (PST) X-Google-Smtp-Source: ALg8bN480JBYIyohVGApMnWLR7ywMYWaaZYt/trh7QvemREah1VjUKYQbseluN+Fvqq36dclPkBG X-Received: by 2002:a17:902:264:: with SMTP id 91mr21006170plc.108.1548662766089; Mon, 28 Jan 2019 00:06:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548662766; cv=none; d=google.com; s=arc-20160816; b=zbKirmHIL0fA4adb0Y9LsHemRcncEu+Wnzmo/YrQXH8GA50pbCYkAqGn/74OBZ3Yid jh4nCW26aShzuHjgDe9TAIEA2fRBzFJi1J9i+MQKlo+1dTmEqNNt0JAJDIN6WxRvKYEs K3CL9w/Ssd+gPhNhyJxalg2NAE3S+LR0chL2pmRNqVMUBUe6dD8o6mi2pVsA0KX9y6w1 pGxmWm2FZDD9e4bIOjF/m15RrRtglQ11lFSw/qcqZ8zpr9EzNWse7PCDl+AiF5HnFGmJ PO+aJartWAJa5WksgtWNtIwrkukaeJAc5nZ3PPH57uz8z8sxx4/J4i0jvl+4vcPWnCD0 n9Ew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=7N+kE9EPr2pqgsl4+arcnpIpJbaWTvKUKdBypqCtbUU=; b=OQDGB/Rb+64jQ5i9kUHigQgMMs2xt1AkA23aCjbZDlozfypLBb6mcuS8uIkFHXWtdi U++5E6WmDbsiMv73z3433AzxtY9r/z6I9waseywQfnDk9ir5Fe2WY6IJpIXLjK3NUcXe 4CA/S+dScijnhdnjtL3iWzinaxS+NYAkV0MmRpos0/2J1ODWB2+FwpnVi9sM+Hgenriw EFd1FJZNrG+mYXl13ngbfc15PvcMqLblGvjLmmCmn5uz/2Dg0Ivt2on7cM0w9Bp6M0i1 1Lc64pEMDa2UvEZ30IYc01Wg+uVJkqqRrqcFgczHG9rX/8CSoztuIuxw+CqA6yAQMvAP otUQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m39si32572730plg.315.2019.01.28.00.05.51; Mon, 28 Jan 2019 00:06:06 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726823AbfA1IFe (ORCPT + 99 others); Mon, 28 Jan 2019 03:05:34 -0500 Received: from metis.ext.pengutronix.de ([85.220.165.71]:39317 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726632AbfA1IFd (ORCPT ); Mon, 28 Jan 2019 03:05:33 -0500 Received: from soja.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:13da]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1go1vA-00057Q-MI; Mon, 28 Jan 2019 09:05:32 +0100 Subject: Re: [PATCH v1 3/3] drivers/tty: increase priority for tty_buffer_worker To: Greg Kroah-Hartman Cc: Linus Torvalds , Jiri Slaby , Pengutronix Kernel Team , lkml References: <20190110101232.9398-1-o.rempel@pengutronix.de> <20190110101232.9398-4-o.rempel@pengutronix.de> <20190110151953.qpat4t7lat6plfk6@pengutronix.de> <20190110163030.GB19693@kroah.com> From: Oleksij Rempel Message-ID: <7a593f3b-0019-c30f-30e8-34eae7b96cf0@pengutronix.de> Date: Mon, 28 Jan 2019 09:05:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190110163030.GB19693@kroah.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:13da X-SA-Exim-Mail-From: o.rempel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10.01.19 17:30, Greg Kroah-Hartman wrote: > On Thu, Jan 10, 2019 at 04:19:53PM +0100, Oleksij Rempel wrote: >>> My gut feel is that if somebody still cares deeply about serial line >>> latency, they should look at trying to see if they can do some of the >>> work directly without the bounce to the workqueue. We use workqueues >>> for a reason, but it's possible that some of it could be avoided at >>> least in special cases... And yours sounds like a special case. >> >> It is for industrial low latency RS-422 based application. The loopback >> test is just easy way to test/reproduce it without additional hardware. >> >> What is good, mainlineable way to implement it? > > What is the real problem your systems are having? Are they serial-port > limited? Is latency a big issue? Trying to tune for a fake workload > isn't the best way to solve anything :) The system in question is a high power laser cutter with live image-based inspection and adjustment of the cutting process. In this setup the RS422 interface is used to control parameters of the laser cutting unit in a tie control loop with the camera. This loops needs to operate at 1000 Hz. The xy-stage moves with a speed of approx. 60m/min, i.e. within 1ms it moves about 1mm. For a high precision control process a jitter of ± 500 us (+/- 0.5mm) is unacceptable. Kind regards, Oleksij Rempel -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |