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 EA901432B0; Mon, 6 Nov 2023 15:18:33 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3851A40A70; Mon, 6 Nov 2023 15:18:18 +0100 (CET) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) by mails.dpdk.org (Postfix) with ESMTP id 4BE8840278 for ; Sun, 5 Nov 2023 10:56:51 +0100 (CET) Received: by mail-wm1-f41.google.com with SMTP id 5b1f17b1804b1-40907b82ab9so26159185e9.1 for ; Sun, 05 Nov 2023 01:56:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scylladb.com; s=google; t=1699178211; x=1699783011; darn=dpdk.org; h=mime-version:user-agent:references:in-reply-to:date:cc:to:from :subject:message-id:from:to:cc:subject:date:message-id:reply-to; bh=TquGQ4iTdCYwqhy6BvAFIFEuxsRqH6zyQPcBREdMATI=; b=v1cuRgi+ryfrG3YCL7DtML2ChBhTQTYBFRHtqhIpppubv3EKSGWKiiVU0pQVRnF9sB drBDmDCl4Toss+Fcc+5nFVh467u1kFvf0V7lgbEXm339rwRLMANvdmlCmnFjs1Ri4gEQ 3+rDso6bT6gzmyh5TmSR4mTOaLG5WhMd7FAFjvXOY8CC0F+olNDdIZmjHAJaoKsaaQd7 FX9Dy9vRl4yBAavAS64x7HNWDlUsCULh+eHwSbBDZdR/Aci4IlORRJLUeA+T/33yykss uinV2TiWK+nDIxlkn5H3Us/QsTKXHcmuKG8x7SAfpVzD9NTb1wDexFlN4d+DP/gKR5W1 qmSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699178211; x=1699783011; h=mime-version:user-agent:references:in-reply-to:date:cc:to:from :subject:message-id:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=TquGQ4iTdCYwqhy6BvAFIFEuxsRqH6zyQPcBREdMATI=; b=mbm0w0NSE1k2D478oGP3nIPfQVWKIYhi57C56ETUyfE+2mCd//8zaQEsrgoq0KGvtG Tv/QagGxVWFy8AoSMQj7qul5CkOM2oQrFwXIoL9eKtaEOkTmaG7HusNagiQVbC9jvK9C dt8VDSGfb66p+3w7LL1vIGGAKIPQINtEf+2I/ddkt8Wi6fNeeKAraGWFY87ArA+H8p1j NeOzaRXaohDQtsREKrRy+gdYNirKkQMgzAChgMM4WvMrhtP1dJZcX2VIRabeQY5bbAay rmRMwR83QobhDc01ZnKvp8xGgeKcNnVWk+vppFGBfyULDZD0xEFsFoZjo4cOEMZzbAJJ gKHQ== X-Gm-Message-State: AOJu0Yy+XcnhOQC+p3UlGFOFve0M7XXm898+B2iS8mVz8c3PLkZS3a6H Hs8KV2ix9lYLG/Uale9dL57DWVn9S7Dwy/l+T4d8yzZSS82CXMv76KGgMEkUenNmb2G9ejEDo2z Jip6astmjNCDxD5NMSniHi524Ayr674CZdqdS9x3Id7E/ltOM+z6si0b0saShz0mt10ooiI46Tf zltCO/Y+uHpA2UOOJycW8j/JxQjNjAHfq4/9SxCmmUc3/QzO1VBqLxilvLk9MhN0lhAjbJLUaZq EM= X-Google-Smtp-Source: AGHT+IG+XKzSy8Dg5mSpEEl5T5KsGTDj1n6XBZhRlZCJyum3/6RS93178mPLPzb81k4J9zgbXJoOSQ== X-Received: by 2002:a05:600c:2942:b0:407:4701:f9e with SMTP id n2-20020a05600c294200b0040747010f9emr8970522wmd.17.1699178210623; Sun, 05 Nov 2023 01:56:50 -0800 (PST) Received: from avi.scylladb.com (system.cloudius-systems.com. [199.203.229.89]) by smtp.gmail.com with ESMTPSA id iv12-20020a05600c548c00b0040641a9d49bsm8529120wmb.17.2023.11.05.01.56.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 Nov 2023 01:56:49 -0800 (PST) Message-ID: <7fa897991d4c5f1d0b91b65ce58276c5fa434bbd.camel@scylladb.com> Subject: Re: configuration of memseg lists number From: Avi Kivity To: Thomas Monjalon , anatoly.burakov@intel.com Cc: david.marchand@redhat.com, bruce.richardson@intel.com, dev@dpdk.org, Kefu Chai Date: Sun, 05 Nov 2023 11:56:47 +0200 In-Reply-To: <3585796.R56niFO833@thomas> References: <3585796.R56niFO833@thomas> Content-Type: multipart/alternative; boundary="=-zTUjaPpNaXJ9Vbhf3yNj" User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 X-CLOUD-SEC-AV-Sent: true X-CLOUD-SEC-AV-Info: scylladb,google_mail,monitor X-Gm-Spam: 0 X-Gm-Phishy: 0 X-Mailman-Approved-At: Mon, 06 Nov 2023 15:18:13 +0100 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 --=-zTUjaPpNaXJ9Vbhf3yNj Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, it makes sense. I'll get around to it "eventually". On Thu, 2023-11-02 at 11:04 +0100, Thomas Monjalon wrote: > Hello, >=20 > While looking at Seastar, I see it uses this patch on top of DPDK: >=20 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0build: add meson options = of max_memseg_lists >=20 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0RTE_MAX_MEMSEG_LISTS =3D = 128 is not enough for high-memory > machines, > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0in our case, we need to i= ncrease it to 8192. > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0so add an option so user = can override it. >=20 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0https://github.com/scylla= db/dpdk/commit/cafaa3cf457584de >=20 > I think we could allow to configure this at runtime, > as we did already for RTE_MAX_MEMZONE: > we've added rte_memzone_max_set() / rte_memzone_max_get(). >=20 > Opinions, comments, volunteers? >=20 >=20 --=-zTUjaPpNaXJ9Vbhf3yNj Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Thanks, it makes sense. I'll get around to it "ev= entually".

On Thu, 2023-11-02 at 11:04 +0100, Thom= as Monjalon wrote:
Hello,

While looking at Seastar, I see it uses this patch on top = of DPDK:

      &= nbsp; build: add meson options of max_memseg_lists

<= /div>
        RTE_MAX_MEMSEG_LI= STS =3D 128 is not enough for high-memory machines,
 &nb= sp;      in our case, we need to increase it = to 8192.
        so a= dd an option so user can override it.


I think we could allow to = configure this at runtime,
as we did already for RTE_MAX_MEMZ= ONE:
we've added rte_memzone_max_set() / rte_memzone_max_get(= ).

Opinions, comments, volunteers?



<= /div> --=-zTUjaPpNaXJ9Vbhf3yNj--