Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp3182101ybi; Tue, 2 Jul 2019 03:29:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqxT285gNUbWYxTpj8cQqbX78MUnwu1Zc1nnDBG6P6CIgHn0oKjeEJbIBJ/xemeuj4ZIMmdu X-Received: by 2002:a63:6b07:: with SMTP id g7mr30951822pgc.325.1562063352755; Tue, 02 Jul 2019 03:29:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562063352; cv=none; d=google.com; s=arc-20160816; b=odTek3b/+ihFv6I1ENWp31X7X+0+R08wcTw5238LvZ8/Sac63chPv30VrAfj6muPE1 TInNYEWhKUo+Po+F3BMlfHzc/xG+LM+pHFjIUwkx/Ntyx6rrffzdAvHKd6q/TTuP+FiU aOd0DRlBQF87G3IedRZCoyxPfSpg/81BlZDogzVOlqIC9ThT/YRBrnKJlEW4uux9/SCI gX9kMev3/zp7JUKZmkpl+p9/wE7nrFzXvG9ytDtSBCoNqfJTGeZDkGmOFon8SJbztI9q 4+nlrqvp3YG3LoEkq13JtamwlYzkPYN6BdElWlAfYl+5c8xNNL0vMVjrGZayQ7qjB22y daRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature; bh=FJAoLq2yYpoyP866NFxrTxDtCZx9jNnhXp1gplkx1G0=; b=itUqP4ErBYfGRJQCUQJ6hbQkwBQblsnVGOXcztOUCmSGZOS1zkhA+3vYl7fnPel/Tw QbFMJT0j/pATvjFX+ivc5h0Y+yUCS5EskPvkyQNYp/jMWvENTnHKv+1N4TEkxm1pzczP HsvfXmFwQ0kJu4tpYcV7dHWkZC5hExbD5uQW3qroE0PDnX5r3RmeVgYotkRUuMi2omfw XdNNvzzgcjrqAVlsr78AR9LXquC5eKMtRdzMa08QlVfL2qN9z76mq+6OlPreuNlh2dH1 FGDc7NE9nwZdNKOCzCgGpp+PK86wvHu5TPOpYhEJ0VqB5VsZyYEr5xoeCO/SjU7Ccogd hv1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=uMRdXIJp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b13si13249833pfb.162.2019.07.02.03.28.58; Tue, 02 Jul 2019 03:29:12 -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; dkim=pass header.i=@linaro.org header.s=google header.b=uMRdXIJp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726102AbfGBK1M (ORCPT + 99 others); Tue, 2 Jul 2019 06:27:12 -0400 Received: from mail-lf1-f67.google.com ([209.85.167.67]:44578 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725867AbfGBK1M (ORCPT ); Tue, 2 Jul 2019 06:27:12 -0400 Received: by mail-lf1-f67.google.com with SMTP id r15so10969225lfm.11 for ; Tue, 02 Jul 2019 03:27:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=FJAoLq2yYpoyP866NFxrTxDtCZx9jNnhXp1gplkx1G0=; b=uMRdXIJpcUIh1Upco8z6RqLjiQ+jSmoT9ixYtVKNUXIufLxE/LzDUVxMmwfeT0D6S9 qs9y3U/wkXQNEsRppMyFot+cnA0nuG/TIZOxyEXI+mbXuhsc6z+9QUZN9fw0WMVhE+zQ fsAPmcRkHaUhLJQLzg0gNBdQjg5ck+Wre2GC4eOm7YCIIQ6gnqRLuezDIwHUHuUFqEBH 0rFrrVmmkgt2C53akTp4oz/w8TJksp0XZX+jVAgyDJJI8wzXCHj4Eh1BEJdTkJoEdxRt AOn6grn5JiU9IHODJj2h/y44OgoiT52glf3j/BVdk5ye69IKfhsGzSHLCfRVaJqTwk02 435g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=FJAoLq2yYpoyP866NFxrTxDtCZx9jNnhXp1gplkx1G0=; b=YxUzFe0PPi7x9as1Gf/tkdrdd9od4b/T2eg6b6f77iSIhH4HRgoMudg9HEY9BuvKhw MhiECO7ZfLz87cdRv04iFkotqh5k5wwgF6RVlCc7twkw9OlOn+0ism/YU90aIiBw2/xj +9TGLe+XZqihOMEUv0ezPVOHx8VK6rpZREzVG9E3edVfc/9U/2WGVacFuxaC3Nkog8Z2 KnxAjNrFn8yVVHApHaCaA6WtpaxhXGs4SsNCuF7GjW1YdDXpp4/rGhcVJF8oy9Oq147G Xdfa3O2lXYbnToZlWtYo12DYPzizRQIfNLHo10ds/qqoo3DVVsuZVmXPZUqUsv3qhaoK nkOA== X-Gm-Message-State: APjAAAWvmX47Bltkgchc/BUJL1PkC48jBBkuu/i7YU+eGrV+b2fTbrAR X0qQsVKs21sWLogDZv37QpshIg== X-Received: by 2002:a19:491d:: with SMTP id w29mr11032597lfa.149.1562063229748; Tue, 02 Jul 2019 03:27:09 -0700 (PDT) Received: from khorivan (59-201-94-178.pool.ukrtel.net. [178.94.201.59]) by smtp.gmail.com with ESMTPSA id c1sm2989071lfh.13.2019.07.02.03.27.08 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 02 Jul 2019 03:27:09 -0700 (PDT) Date: Tue, 2 Jul 2019 13:27:07 +0300 From: Ivan Khoronzhuk To: Jesper Dangaard Brouer Cc: grygorii.strashko@ti.com, hawk@kernel.org, davem@davemloft.net, ast@kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, xdp-newbies@vger.kernel.org, ilias.apalodimas@linaro.org, netdev@vger.kernel.org, daniel@iogearbox.net, jakub.kicinski@netronome.com, john.fastabend@gmail.com Subject: Re: [PATCH v5 net-next 1/6] xdp: allow same allocator usage Message-ID: <20190702102700.GA4510@khorivan> Mail-Followup-To: Jesper Dangaard Brouer , grygorii.strashko@ti.com, hawk@kernel.org, davem@davemloft.net, ast@kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, xdp-newbies@vger.kernel.org, ilias.apalodimas@linaro.org, netdev@vger.kernel.org, daniel@iogearbox.net, jakub.kicinski@netronome.com, john.fastabend@gmail.com References: <20190630172348.5692-1-ivan.khoronzhuk@linaro.org> <20190630172348.5692-2-ivan.khoronzhuk@linaro.org> <20190701134059.71757892@carbon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190701134059.71757892@carbon> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 01, 2019 at 01:40:59PM +0200, Jesper Dangaard Brouer wrote: > >I'm very skeptical about this approach. > >On Sun, 30 Jun 2019 20:23:43 +0300 >Ivan Khoronzhuk wrote: > >> XDP rxqs can be same for ndevs running under same rx napi softirq. >> But there is no ability to register same allocator for both rxqs, >> by fact it can same rxq but has different ndev as a reference. > >This description is not very clear. It can easily be misunderstood. > >It is an absolute requirement that each RX-queue have their own >page_pool object/allocator. (This where the performance comes from) as >the page_pool have NAPI protected array for alloc and XDP_DROP recycle. > >Your driver/hardware seems to have special case, where a single >RX-queue can receive packets for two different net_device'es. > >Do you violate this XDP devmap redirect assumption[1]? >[1] https://github.com/torvalds/linux/blob/v5.2-rc7/kernel/bpf/devmap.c#L324-L329 Seems that yes, but that's used only for trace for now. As it runs under napi and flush clear dev_rx i must do it right in the rx_handler. So next patchset version will have one patch less. Thanks! > > >> Due to last changes allocator destroy can be defered till the moment >> all packets are recycled by destination interface, afterwards it's >> freed. In order to schedule allocator destroy only after all users are >> unregistered, add refcnt to allocator object and schedule to destroy >> only it reaches 0. > >The guiding principles when designing an API, is to make it easy to >use, but also make it hard to misuse. > >Your API change makes it easy to misuse the API. As it make it easy to >(re)use the allocator pointer (likely page_pool) for multiple >xdp_rxq_info structs. It is only valid for your use-case, because you >have hardware where a single RX-queue delivers to two different >net_devices. For other normal use-cases, this will be a violation. > >If I was a user of this API, and saw your xdp_allocator_get(), then I >would assume that this was the normal case. As minimum, we need to add >a comment in the code, about this specific/intended use-case. I >through about detecting the misuse, by adding a queue_index to >xdp_mem_allocator, that can be checked against, when calling >xdp_rxq_info_reg_mem_model() with another xdp_rxq_info struct (to catch >the obvious mistake where queue_index mismatch). I can add, but not sure if it has or can have some conflicts with another memory allocators, now or in future. Main here to not became a cornerstone in some not obvious use-cases. So, for now, let it be in this way: --- a/include/net/xdp_priv.h +++ b/include/net/xdp_priv.h @@ -19,6 +19,7 @@ struct xdp_mem_allocator { struct delayed_work defer_wq; unsigned long defer_warn; unsigned long refcnt; + u32 queue_index; }; #endif /* __LINUX_NET_XDP_PRIV_H__ */ diff --git a/net/core/xdp.c b/net/core/xdp.c index a44621190fdc..c4bf29810f4d 100644 --- a/net/core/xdp.c +++ b/net/core/xdp.c @@ -324,7 +324,7 @@ static bool __is_supported_mem_type(enum xdp_mem_type type) return true; } -static struct xdp_mem_allocator *xdp_allocator_get(void *allocator) +static struct xdp_mem_allocator *xdp_allocator_find(void *allocator) { struct xdp_mem_allocator *xae, *xa = NULL; struct rhashtable_iter iter; @@ -336,7 +336,6 @@ static struct xdp_mem_allocator *xdp_allocator_get(void *allocator) while ((xae = rhashtable_walk_next(&iter)) && !IS_ERR(xae)) { if (xae->allocator == allocator) { - xae->refcnt++; xa = xae; break; } @@ -386,9 +385,13 @@ int xdp_rxq_info_reg_mem_model(struct xdp_rxq_info *xdp_rxq, } } - xdp_alloc = xdp_allocator_get(allocator); + xdp_alloc = xdp_allocator_find(allocator); if (xdp_alloc) { + if (xdp_alloc->queue_index != xdp_rxq->queue_index) + return -EINVAL; + xdp_rxq->mem.id = xdp_alloc->mem.id; + xdp_alloc->refcnt++; return 0; } @@ -406,6 +409,7 @@ int xdp_rxq_info_reg_mem_model(struct xdp_rxq_info *xdp_rxq, xdp_alloc->mem = xdp_rxq->mem; xdp_alloc->allocator = allocator; xdp_alloc->refcnt = 1; + xdp_alloc->queue_index = xdp_rxq->queue_index; /* Insert allocator into ID lookup table */ ptr = rhashtable_insert_slow(mem_id_ht, &id, &xdp_alloc->node); Jesper, are you Ok with this version? > > >> Signed-off-by: Ivan Khoronzhuk >> --- >> include/net/xdp_priv.h | 1 + >> net/core/xdp.c | 46 ++++++++++++++++++++++++++++++++++++++++++ >> 2 files changed, 47 insertions(+) >> >> diff --git a/include/net/xdp_priv.h b/include/net/xdp_priv.h >> index 6a8cba6ea79a..995b21da2f27 100644 >> --- a/include/net/xdp_priv.h >> +++ b/include/net/xdp_priv.h >> @@ -18,6 +18,7 @@ struct xdp_mem_allocator { >> struct rcu_head rcu; >> struct delayed_work defer_wq; >> unsigned long defer_warn; >> + unsigned long refcnt; >> }; >> >> #endif /* __LINUX_NET_XDP_PRIV_H__ */ >> diff --git a/net/core/xdp.c b/net/core/xdp.c >> index b29d7b513a18..a44621190fdc 100644 >> --- a/net/core/xdp.c >> +++ b/net/core/xdp.c >> @@ -98,6 +98,18 @@ bool __mem_id_disconnect(int id, bool force) >> WARN(1, "Request remove non-existing id(%d), driver bug?", id); >> return true; >> } >> + >> + /* to avoid calling hash lookup twice, decrement refcnt here till it >> + * reaches zero, then it can be called from workqueue afterwards. >> + */ >> + if (xa->refcnt) >> + xa->refcnt--; >> + >> + if (xa->refcnt) { >> + mutex_unlock(&mem_id_lock); >> + return true; >> + } >> + >> xa->disconnect_cnt++; >> >> /* Detects in-flight packet-pages for page_pool */ >> @@ -312,6 +324,33 @@ static bool __is_supported_mem_type(enum xdp_mem_type type) >> return true; >> } >> >> +static struct xdp_mem_allocator *xdp_allocator_get(void *allocator) > >API wise, when you have "get" operation, you usually also have a "put" >operation... It's not part of external API. I propose to rename it on xdp_allocator_find() as in above diff. What do you say? > >> +{ >> + struct xdp_mem_allocator *xae, *xa = NULL; >> + struct rhashtable_iter iter; >> + >> + mutex_lock(&mem_id_lock); >> + rhashtable_walk_enter(mem_id_ht, &iter); >> + do { >> + rhashtable_walk_start(&iter); >> + >> + while ((xae = rhashtable_walk_next(&iter)) && !IS_ERR(xae)) { >> + if (xae->allocator == allocator) { >> + xae->refcnt++; >> + xa = xae; >> + break; >> + } >> + } >> + >> + rhashtable_walk_stop(&iter); >> + >> + } while (xae == ERR_PTR(-EAGAIN)); >> + rhashtable_walk_exit(&iter); >> + mutex_unlock(&mem_id_lock); >> + >> + return xa; >> +} >> + >> int xdp_rxq_info_reg_mem_model(struct xdp_rxq_info *xdp_rxq, >> enum xdp_mem_type type, void *allocator) >> { >> @@ -347,6 +386,12 @@ int xdp_rxq_info_reg_mem_model(struct xdp_rxq_info *xdp_rxq, >> } >> } >> >> + xdp_alloc = xdp_allocator_get(allocator); >> + if (xdp_alloc) { >> + xdp_rxq->mem.id = xdp_alloc->mem.id; >> + return 0; >> + } >> + > >The allocator pointer (in-practice) becomes the identifier for the >mem.id (which rhashtable points to xdp_mem_allocator object). So, you have no obj against it? [...] -- Regards, Ivan Khoronzhuk