From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D75F7C433EF for ; Thu, 30 Jun 2022 23:39:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231640AbiF3Xjz (ORCPT ); Thu, 30 Jun 2022 19:39:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231936AbiF3Xjy (ORCPT ); Thu, 30 Jun 2022 19:39:54 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D163645066 for ; Thu, 30 Jun 2022 16:39:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1656632390; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=b9GVsLYDNIjnA5AzRP3UDciaV6BcKEPUnpIHk/sNuEM=; b=IZjCB/fpb1ho8LGHkfGi7P3QCDmnTuUbmK7N9cgjnAz7l8+Z9fbm0y4/zhx9t9GOkXucPj qq5gWb5Ju4C0aO3NCmUGR/eCfJEickqdSB28fzjTsncabVdfWAUBqD8dp3wftxtmzLZ+Cq fkqfcBVwHovG8C37BGgSm7Ji4OcGh5s= Received: from mail-qk1-f199.google.com (mail-qk1-f199.google.com [209.85.222.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-252-sEfFx1cqMOOo5JMXvbj_Zg-1; Thu, 30 Jun 2022 19:39:48 -0400 X-MC-Unique: sEfFx1cqMOOo5JMXvbj_Zg-1 Received: by mail-qk1-f199.google.com with SMTP id bj2-20020a05620a190200b005084968bb24so531991qkb.23 for ; Thu, 30 Jun 2022 16:39:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b9GVsLYDNIjnA5AzRP3UDciaV6BcKEPUnpIHk/sNuEM=; b=dTm8eUbqpimr6UX4QXQvvYTXK8d9NJOENwttde3IOsITiezVBo6KnIzmHuewYO4zOW NgrG6ZFV+zkdkeubA0HaGI0O+tC8gulGGmZ2lLA4pAgdO8b8T5mdTQEigrOhesbdhz9M 75b+2CpBlX3sOAP4y69udGeHG2lFXIi/FN/PCnReuK+k8fQ2VUuU2szFpEGPnINWQcex 4xJNHQrSRL+YtWQHnWGmGvwcYe8rN4cXS+X+DO5gNTf2VVibXje2tI2FTEjQ9jWS72g+ lzCpP4ulmR+E5qz8Gq5i2YwXSLzmJWy1HKFwDTaSGWgyC0gtGVfSo7bQvvQD82U7GvO1 +L7Q== X-Gm-Message-State: AJIora/DZ3vdgyZHTFyt98XEPaH7pWNKGU+Zn7TWeeUk5rasWazq2q23 FGPWFuansrBUQgvzYhrpVJ25U5lnkrL0UNQIMNb2K0FkQBGn8T8ixNL2zBRlO6a6weZvMSYhH6o eX0sC0h/TgOenidaAmZ8AuQYhN4M6jBgdI2S9Ew== X-Received: by 2002:a05:622a:90a:b0:31b:899:3070 with SMTP id bx10-20020a05622a090a00b0031b08993070mr10244056qtb.470.1656632388449; Thu, 30 Jun 2022 16:39:48 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v+2gxM//Gl1DZFl6EN2ARpld2eu3hEMQxpCI5Q3r1GZUtr7fZAogE+1KHvIXzDa0sfDQsYXVT6ti1sU0OHBY8= X-Received: by 2002:a05:622a:90a:b0:31b:899:3070 with SMTP id bx10-20020a05622a090a00b0031b08993070mr10244044qtb.470.1656632388282; Thu, 30 Jun 2022 16:39:48 -0700 (PDT) MIME-Version: 1.0 References: <20220620134018.62414-1-miquel.raynal@bootlin.com> <20220620134018.62414-3-miquel.raynal@bootlin.com> <20220627104303.5392c7f6@xps-13> <20220628095821.36811c5c@xps-13> <20220630101416.4dc42f29@xps-13> In-Reply-To: From: Alexander Aring Date: Thu, 30 Jun 2022 19:39:37 -0400 Message-ID: Subject: Re: [PATCH wpan-next v3 2/4] net: ieee802154: Add support for inter PAN management To: Miquel Raynal Cc: Alexander Aring , Stefan Schmidt , linux-wpan - ML , "David S. Miller" , Jakub Kicinski , Paolo Abeni , Eric Dumazet , Network Development , David Girault , Romuald Despres , Frederic Blain , Nicolas Schodet , Thomas Petazzoni Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-wpan@vger.kernel.org Hi, On Thu, Jun 30, 2022 at 7:27 PM Alexander Aring wrote: ... > > Why not move this decision to the user as well? The kernel will wait > for the reason? This isn't required to be fast and the decision may > depend on the current pan management... to be clear here, that this will then and on some coordinator only use a user space daemon which manages whatever is needed for assoc/deassoc management e.g. how short-addresses are allocated, etc. That should also not be part of the kernel, if so then same strategy as we have a user space replacement for it? - Alex