Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4216449ybi; Tue, 18 Jun 2019 14:03:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqwDGWHbvLX6wDlj88yxOBXHuNwrtHOkcrxo3epTIhbUC5gSk775qv0rWVV5Wn6dZf20ksYI X-Received: by 2002:a63:3501:: with SMTP id c1mr4498687pga.115.1560891797626; Tue, 18 Jun 2019 14:03:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560891797; cv=none; d=google.com; s=arc-20160816; b=viGALtgDHKi+4a2NZuN3kcXwp502r/DYX/NNsHMiRbPaTp6scpJQFpRv7egjk9XFqv /h+QsnUlGdN8zZLa64CcayhIHY5vtKXDoL482mxtt4pjix/81wtYQN3lfaCdFdPZrUoh 8XQNteKj3toBETTTJ/baHJCkIjRugFWiTWPP+PkCQv4AKYzvUyplVfc8or5DSXVH9YlG VJQ029R0hdpoQAnwNDQGeHjJSiZWvdzoNlS/aCvHrM1munONFQfmkGeAFGVvO/NlBsQC j3Bfr4oO5/6DAWqlj3K7FIBP8x8CPxzK6OEniGkQ2KncsuOXpxObk+hAWIT0D4TJLy82 DM5A== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=TyZqX1ceCpk8/1QDtwRnV2B413WAZcaLpdj2WAkyH5Y=; b=F4QYCTskYWBNk8KwjLb+hre09vCI+J2/l0vT2nQOGxLadSK68vrUHIS2gjgb7fa5CT 9sWbKFEEWOxsR7pWXMRout0AOZYCELewNaSfEH7Aqdaw5LRma/BZylSah/yvtx7E5oO/ bzEKoRyvS5oVPXkmB5HQ3Z/orqUvaf+Kqx1wN5HlGR9kEV+GhRbqv5Mchd57SsTo6UUf /Mifdh6SbCYlrixaqfyrEYuA0/rTeukqn8Wumi19qOItp02HBV9AZATyYJEkmq7Pg9xt A7pyqWjeUI/3SffIF9/cx2HnFa7EJj3mBHixeV0PWnY9/oQqGlEPPOD8wCCcEc78q+6t 7dBg== 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 131si15115187pfu.165.2019.06.18.14.03.01; Tue, 18 Jun 2019 14:03:17 -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 S1730714AbfFRVCi (ORCPT + 99 others); Tue, 18 Jun 2019 17:02:38 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:48164 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730102AbfFRVCi (ORCPT ); Tue, 18 Jun 2019 17:02:38 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hdLFE-0007LA-Ng; Tue, 18 Jun 2019 23:02:20 +0200 Message-ID: <6e7f0fb2f85d5062a9e23d37c47d311e10aa4624.camel@sipsolutions.net> Subject: Re: [PATCH v2 00/17] net: introduce Qualcomm IPA driver From: Johannes Berg To: Arnd Bergmann Cc: Alex Elder , abhishek.esse@gmail.com, Ben Chan , Bjorn Andersson , cpratapa@codeaurora.org, David Miller , Dan Williams , DTML , Eric Caruso , evgreen@chromium.org, Ilias Apalodimas , Linux ARM , linux-arm-msm@vger.kernel.org, Linux Kernel Mailing List , linux-soc@vger.kernel.org, Networking , Subash Abhinov Kasiviswanathan , syadagir@codeaurora.org Date: Tue, 18 Jun 2019 23:02:18 +0200 In-Reply-To: (sfid-20190618_225543_624686_3B7D51E7) References: <380a6185-7ad1-6be0-060b-e6e5d4126917@linaro.org> <066e9b39f937586f0f922abf801351553ec2ba1d.camel@sipsolutions.net> <613cdfde488eb23d7207c7ba6258662702d04840.camel@sipsolutions.net> (sfid-20190618_225543_624686_3B7D51E7) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-06-18 at 22:55 +0200, Arnd Bergmann wrote: > On Tue, Jun 18, 2019 at 10:36 PM Johannes Berg > wrote: > > > > On Tue, 2019-06-18 at 21:59 +0200, Arnd Bergmann wrote: > > > > > > From my understanding, the ioctl interface would create the lower > > > netdev after talking to the firmware, and then user space would use > > > the rmnet interface to create a matching upper-level device for that. > > > This is an artifact of the strong separation of ipa and rmnet in the > > > code. > > > > Huh. But if rmnet has muxing, and IPA supports that, why would you ever > > need multiple lower netdevs? > > From my reading of the code, there is always exactly a 1:1 relationship > between an rmnet netdev an an ipa netdev. rmnet does the encapsulation/ > decapsulation of the qmap data and forwards it to the ipa netdev, > which then just passes data through between a hardware queue and > its netdevice. I'll take your word for it. Seems very odd, given that the whole point of the QMAP header seems to be ... muxing? > [side note: on top of that, rmnet also does "aggregation", which may > be a confusing term that only means transferring multiple frames > at once] Right, but it's not all that much interesting in the context of this discussion. > Sure, I definitely understand what you mean, and I agree that would > be the right way to do it. All I said is that this is not how it was done > in rmnet (this was again my main concern about the rmnet design > after I learned it was required for ipa) ;-) :-) Well, I guess though if the firmware wants us to listen to those on/off messages we'll have to do that one way or the other. Oh. Maybe it's just *because* rmnet is layered on top, and thus you fundamentally cannot do flow control the way I described - not because you have multiple session on the same hardware ring, but because you abstracted the hardware ring away too much ... johannes