Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1364107imm; Wed, 10 Oct 2018 13:21:38 -0700 (PDT) X-Google-Smtp-Source: ACcGV61gGsvX1J7i4uvXs4QkGn/pZdy61F5e44iqoQ0d5ayTwxViFjb7dVK22LtWghIKqvW6jc+d X-Received: by 2002:a63:924e:: with SMTP id s14-v6mr22333794pgn.141.1539202898940; Wed, 10 Oct 2018 13:21:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539202898; cv=none; d=google.com; s=arc-20160816; b=xm8IvB9DixfovMEBd4eAsQ5E1OoIzHYTJtuh4gOCqiPYCvFOHCuOfL0+MpmiMUiiLC eRZuHFwxvmeDzFvp+fF/sVuQtHyK4Om+Gs0hkzZm6B6tujcWeW61i75NAjDFnWm0jz0l R90A4z+QikNJevcdha6s1q+E1HFjRb9Y1/kdAxEYzrTzqmHDhXrM8TqNdYuojQch4NVe rLNnukNQLKAFsO4EEBqz2zqmgNRkrskU60prLEtynjcdDuCgQ4tbaAM/eUXAgRtmpTtr wipr9cpsomzE+1XwBOPKxZ+TjcL0TLVgAwiOsFDh1ldbpZH2qNWEE2r73J3K6lMEJ3A7 t9KA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date; bh=ASWQcczXTLkjilhDf2MxnYUAAiquqoLQbyiFlPFP1dM=; b=YO/CaW2gemMtYelJ7PdYsOFqsUIT87wKe6dLYiXjEItQDHewJkndsS+udfv11gVXtC jK1d/5kgNjAqg2rT8rS3QKxRqzuqDA+tNid3KdMLH+Fn5MCIztI+tiCZWlMZv89u9Ohc q474JXh1dT3T/d73mm2zqe/SSsRLmDQQIuOo9ac//cO81//PKL9raFwlnsdjWHq4J9c4 nGrpHFAxXfzixvwfAtgc+99W+eaSi0t5Hu2QSkK2jXktPbfy8Rpir0AhBtaqrm/WpBV6 rb5lmOFmf++wdncnHZcbjHag3pOUKfh6A0T59TirNiVXVhIYJd+Q0bGP0i6QIr6r5ooP yMhg== 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 ba8-v6si620222plb.74.2018.10.10.13.21.23; Wed, 10 Oct 2018 13:21:38 -0700 (PDT) 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 S1727751AbeJKDon convert rfc822-to-8bit (ORCPT + 99 others); Wed, 10 Oct 2018 23:44:43 -0400 Received: from terminus.zytor.com ([198.137.202.136]:44885 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727478AbeJKDom (ORCPT ); Wed, 10 Oct 2018 23:44:42 -0400 Received: from [10.171.235.234] ([192.55.54.59]) (authenticated bits=0) by mail.zytor.com (8.15.2/8.15.2) with ESMTPSA id w9AKKoIh1611568 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 10 Oct 2018 13:20:50 -0700 Date: Wed, 10 Oct 2018 13:20:48 -0700 User-Agent: K-9 Mail for Android In-Reply-To: <20181010211717.30c1f052@alans-desktop> References: <3fcef1c1-d746-ae82-c0e6-f079b1a53ffb@zytor.com> <20181010211717.30c1f052@alans-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: Insanely high baud rates To: Alan Cox CC: linux-serial@vger.kernel.org, Linux Kernel Mailing List , Greg Kroah-Hartman , Jiri Slaby , Johan Hovold , Alexander Viro From: hpa@zytor.com Message-ID: <16D6AB22-697E-498C-A5B2-3AD90B567E86@zytor.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On October 10, 2018 1:17:17 PM PDT, Alan Cox wrote: >On Tue, 9 Oct 2018 12:19:04 -0700 >"H. Peter Anvin" wrote: > >> [Resending to a wider audience] >> >> In trying to get the termios2 interface actually implemented in >glibc, >> the question came up if we will ever care about baud rates in excess >of >> 4 Gbps, even in the relatively remote future. > >Even RS485 at 4MBits involves deep magic. I think we are fairly safe. >Not >only that but our entire tty layer isn't capable of sustaining anything >even remotely in that range. > >I think its non issue. > >Alan I'm mostly wondering if it is worth future-proofing for new transports. It sounds like we can have a consensus on leaving the upper 4 bits of the speed fields reserved, but leave the details of implementation for the future? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.