Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5851416ybi; Tue, 4 Jun 2019 13:27:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqyT9DncA6PmEsTFCkSCQxEUFrrlKf4ycOZQyg1Wb3KbwwZ3vjuGttSRzxI1gMKGAqLV9x1h X-Received: by 2002:a63:1663:: with SMTP id 35mr501167pgw.253.1559680038684; Tue, 04 Jun 2019 13:27:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559680038; cv=none; d=google.com; s=arc-20160816; b=JLEDsDW2WylvGOVUlo6zkrtxq6lTo0LPBdkI/JBdGI4yNS3ZquYOcP++Veh2V33LB4 iVqbks75teSbDd2gBeDwZ7mxhgGttD0WhiJ/LdfMyIWlLIRbAWsD5Fn+MsNHLbuscnSU NGUuO3KfInen3q4a8gi58uW0+jaiVbh8VHR6WFec3CnajDEReXfELRm7sbYs7yGQTIIU Q2Xt+Lecp7weD7yO2Utx11IgO8XOntHTQo+JUf7GJ+psZPop0rAq3QSft/fr3W1D5xOF LtFlv1jTS+mO+eRrGSTWN6lohF7X6e0JATu6k/KiEpS/ePBIXEzlKQ7Oayr36/viSYC1 RXwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=kRWHmlTazXX9nh3l+uCl+QUYh7joRupEOxTxYsi6yow=; b=rRQn3M5H9RAUsY+AJ9izYGfu3k1Op/LUB1x1Cg/DuJsvsXOF6/rNKfVXZQC6srnPO0 wX/7xkXQegmgT2Q2CjXt4Ag+Sp/bHpBjHYUPmLm1+vqJYVyTbXTtTG0BhsHqkvpRlMeU yjicJAuCcUwXc6Gz/aVaXRs2ZH6lst/baNTM6+5XFVaVBCsZN8z/kC81MSvZ6ZDQVOMi WyRWH2WahMQ+A4EEXXpzkCvcHqh9Mu8MjopzBzGF/PwAF/rg3HgtDfVvssCOuVshoSTy rD0NsEM9U1ysTprDahuCh/DAGXcJ+aJBNg9JTSWup9XQq+cFhwJkex4a9udP1yAFmVMQ VrzQ== 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 l6si21485889pgp.382.2019.06.04.13.27.01; Tue, 04 Jun 2019 13:27:18 -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 S1726530AbfFDUE2 (ORCPT + 99 others); Tue, 4 Jun 2019 16:04:28 -0400 Received: from mail-qk1-f193.google.com ([209.85.222.193]:45233 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726179AbfFDUE2 (ORCPT ); Tue, 4 Jun 2019 16:04:28 -0400 Received: by mail-qk1-f193.google.com with SMTP id s22so3680282qkj.12; Tue, 04 Jun 2019 13:04:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kRWHmlTazXX9nh3l+uCl+QUYh7joRupEOxTxYsi6yow=; b=SXym818ZY4smWXmvcE8o6563iTfvy9jWjvzneIlUJ0KNSaAYSAvPo6xhPb+Wz/Wts4 BNe5iFhu64pMgFczNJCTLx/iPJqLtHERbO9poa/paXZZ/nA2Y+1ZTleHYf96HT30TAdC FXvJPtekAFeA5MwxyytMoCoYyx/LP6PBev3VZHIkdq6u5SWoZo7dvzHiq5VqQACnF2fV erBgkR/gsR0mAC8Bx5IWH8+IyQW/9bEDCgu2IsIavL4BS89bXdu0Q4Ao1K8LyBxArK13 ml6HdIdwmtOwW3x59uzxTA5lKiTl2v5V+QE2U0/S6jScsSywwbbsCZc2Fdmae2DlFe8s S7kg== X-Gm-Message-State: APjAAAWUwLJ/K1XrwnSPzN4kl9/FZxIUNPxdpd4NPjXSbiRoLL95LgZu il7lndNrbyezfTu1dC/igIWHROGbC+dD9OxK1aI= X-Received: by 2002:a37:a4d3:: with SMTP id n202mr28029003qke.84.1559678666645; Tue, 04 Jun 2019 13:04:26 -0700 (PDT) MIME-Version: 1.0 References: <20190531035348.7194-1-elder@linaro.org> <065c95a8-7b17-495d-f225-36c46faccdd7@linaro.org> <20190531233306.GB25597@minitux> <040ce9cc-7173-d10a-a82c-5186d2fcd737@linaro.org> In-Reply-To: From: Arnd Bergmann Date: Tue, 4 Jun 2019 22:04:09 +0200 Message-ID: Subject: Re: [PATCH v2 00/17] net: introduce Qualcomm IPA driver To: Dan Williams Cc: Alex Elder , Subash Abhinov Kasiviswanathan , Bjorn Andersson , David Miller , Ilias Apalodimas , evgreen@chromium.org, Ben Chan , Eric Caruso , cpratapa@codeaurora.org, syadagir@codeaurora.org, abhishek.esse@gmail.com, Networking , DTML , Linux Kernel Mailing List , linux-soc@vger.kernel.org, Linux ARM , linux-arm-msm@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 4, 2019 at 5:18 PM Dan Williams wrote: > On Tue, 2019-06-04 at 10:13 +0200, Arnd Bergmann wrote: > > > > Can you describe what kind of multiplexing is actually going on? > > I'm still unclear about what we actually use multiple logical > > interfaces for here, and how they relate to one another. > > Each logical interface represents a different "connection" (PDP/EPS > context) to the provider network with a distinct IP address and QoS. > VLANs may be a suitable analogy but here they are L3+QoS. > > In realistic example the main interface (say rmnet0) would be used for > web browsing and have best-effort QoS. A second interface (say rmnet1) > would be used for VOIP and have certain QoS guarantees from both the > modem and the network itself. > > QMAP can also aggregate frames for a given channel (connection/EPS/PDP > context/rmnet interface/etc) to better support LTE speeds. Thanks, that's a very helpful explanation! Is it correct to say then that the concept of having those separate connections would be required for any proper LTE modem implementation, but the QMAP protocol (and based on that, the rmnet implementation) is Qualcomm specific and shared only among several generations of modems from that one vendor? You mentioned the need to have a common user space interface for configuration, and if the above is true, I agree that we should try to achieve that, either by ensuring rmnet is generic enough to cover other vendors (and non-QMAP clients), or by creating a new user level interface that IPA/rmnet can be adapted to. Arnd