From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C9B21A0543; Tue, 4 Oct 2022 13:36:11 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4268840DFB; Tue, 4 Oct 2022 13:36:11 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 39E0840DDC for ; Tue, 4 Oct 2022 13:36:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664883368; 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=fGGuEXUbPUYlrZlkSqAJXPE73y1ByI41MvltaFDEoLc=; b=G7JioBc9IUlE+TmQ5rqyPrKPx76pkoV+5epr4ztZhIdrIlKwssvyZEEea8q9cZZ/8BCLVt 251to+ux3YG84jVjOGbuqm4GcCy2QdUnTqmNjPDLXNAwVqNeOH6DHvOoUFSfTCkJWTCKaY 54n4iWtcG1OioL1Y073WzxODLQLsm6k= Received: from mail-pj1-f70.google.com (mail-pj1-f70.google.com [209.85.216.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-647-L1o-OHGHMuWygCmx5EGGnw-1; Tue, 04 Oct 2022 07:36:05 -0400 X-MC-Unique: L1o-OHGHMuWygCmx5EGGnw-1 Received: by mail-pj1-f70.google.com with SMTP id pq17-20020a17090b3d9100b0020a4c65c3a9so4262528pjb.0 for ; Tue, 04 Oct 2022 04:36:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=fGGuEXUbPUYlrZlkSqAJXPE73y1ByI41MvltaFDEoLc=; b=lf6a8cVGn1/LttAtrt+KQZNWb2U/n519Fhpxho8v7DelVkYSn4ddKv5bIl0FYQfMcx voBUq0gpveSA7YRbeY+hkEL5ICchw0CKPewfW/DmvH/N/++HLQClz/5STSe3ueujYkLY cYWMo7H1aw9Y00Ftt8ViNGLJZJRnyzypU1w2pjQgk7N89naZ+bXo5TNjuZRNb+/yXHkG kTwNeAvt3iGnD51MrB0pLXOrxXWFe5cEtJBQeT1sAFUeXKvcFIQIHQHPFBlR4+80yrYY LZwZHS/KocMKWuZSvHs3uxFs8UR6tqskSsDGZQ0r9+Km2L0rdyOoCVNzZq+BMQ1hknXp P60A== X-Gm-Message-State: ACrzQf3EWeOQbTUpiv7HAeoT7+Rrl3glm2MIAlUontRlKyY/dWiP3vUX 3cR9cVX9UNi9ZIiXQmmRrftz9p+pEnSdUCUpIOC1d0I70KXLC7lwPQw4SElXv+annlP6SGOrM86 ymE3ItKBeF968BC0LwUo= X-Received: by 2002:a62:c584:0:b0:558:2095:e5ed with SMTP id j126-20020a62c584000000b005582095e5edmr27211616pfg.64.1664883363553; Tue, 04 Oct 2022 04:36:03 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4SWEwmamk1VjWtNJwn0hCMwx3yhph8tYGaqEEGQflmYC0PsPwb8iKOYO//gHT01atP3Zxvxt/DaKyF6zo+fz8= X-Received: by 2002:a62:c584:0:b0:558:2095:e5ed with SMTP id j126-20020a62c584000000b005582095e5edmr27211600pfg.64.1664883363285; Tue, 04 Oct 2022 04:36:03 -0700 (PDT) MIME-Version: 1.0 References: <20220929122311.1263-1-olivier.matz@6wind.com> In-Reply-To: From: David Marchand Date: Tue, 4 Oct 2022 13:35:51 +0200 Message-ID: Subject: Re: [PATCH] mem: fix API doc about allocation on secondary processes To: Olivier Matz Cc: Honnappa Nagarahalli , "dev@dpdk.org" , Anatoly Burakov , Andrew Rybchenko , Konstantin Ananyev , nd X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, Sep 30, 2022 at 3:19 PM Honnappa Nagarahalli wrote: > > Since 10 years, memzone allocation is allowed on secondary processes. Now > > it's time to update the documentation accordingly. > > > > At the same time, fix mempool, mbuf and ring documentation which rely on > > memzones internally. > > > > Bugzilla ID: 1074 > > Fixes: 916e4f4f4e45 ("memory: fix for multi process support") Cc: stable@dpdk.org > > > > Signed-off-by: Olivier Matz > Reviewed-by: Honnappa Nagarahalli Applied, thanks. -- David Marchand