From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) by sourceware.org (Postfix) with ESMTPS id D698C3858289 for ; Wed, 8 Mar 2023 14:53:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D698C3858289 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=opensuse.org Authentication-Results: sourceware.org; spf=none smtp.mailfrom=cristianrodriguez.net Received: by mail-io1-f47.google.com with SMTP id e11so6870107ioe.3 for ; Wed, 08 Mar 2023 06:53:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678287238; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=vKeihgnmrYWKWPdghVHKNSUmToYb4t4Nu1WkqwaLf9Q=; b=PzDAPrZau7BAxdEM7DVEQjcLUNGuQNhk9bGkkSfB/SynhoU1D1E40YTIPo64xIxumW itvKHUgqTOp9p6heUcQsVqvZ0pIEUrJTUCbvHFRqtml9Jr5TPA66i2hUY9vjKx8B488x s7u7ucxluFlQQ4kIUz2n+FdIOSsvkFK3X+OaGDo4dyn8+Z6o+zxuBhs+VgqCC8r4AiDk 7ObJJHD6IHNurAwwFpvJtKxov2HkQsFzMMBZ69oZEfGswNRlsvERWOdZ8LgRJmZa6UGP 9fCLJSbDWAhVRJrwDt1nEOtXK/20xm2vD8VFjLHsFtDpRh89hHKbXDwlWaulvSqCmJmn d16A== X-Gm-Message-State: AO0yUKUKNs/ULTPdrUh8H9EfOcdmu5+jCWgg5K/JHVVKOMXXta3jn65J UAEu+2q6bJV4bGXXbJhq8+spjthGss/fTK4Jp4Oj2g== X-Google-Smtp-Source: AK7set9jig7xbBnempen0wzYYcyhMcW5Fb/3GKEV4AZZkVj4gU/X02+WPUNeW+El0ovpv13h+Zq0WP5lxz1RwbPNdoM= X-Received: by 2002:a6b:7902:0:b0:745:70d7:4962 with SMTP id i2-20020a6b7902000000b0074570d74962mr8408428iop.0.1678287237875; Wed, 08 Mar 2023 06:53:57 -0800 (PST) MIME-Version: 1.0 References: <87pm9j4azf.fsf@oracle.com> <87mt4n49ak.fsf@oracle.com> In-Reply-To: <87mt4n49ak.fsf@oracle.com> From: =?UTF-8?Q?Cristian_Rodr=C3=ADguez?= Date: Wed, 8 Mar 2023 11:53:46 -0300 Message-ID: Subject: Re: [RFC] Stack allocation, hugepages and RSS implications To: Cupertino Miranda Cc: libc-alpha@sourceware.org, "Jose E. Marchesi" , Elena Zannoni , Cupertino Miranda Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00,HEADER_FROM_DIFFERENT_DOMAINS,KAM_DMARC_NONE,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Wed, Mar 8, 2023 at 11:17=E2=80=AFAM Cupertino Miranda via Libc-alpha wrote: > > > Hi everyone, > In any case, I wonder if there is an actual use case where an hugepage wo= uld > survive glibc stack allocation and will bring an actual benefit. > > Looking forward for your comments. I think you could just post a patch to disable hugepages for this allocatio= n. Are you sure this is the only case though ? There are probably several cases where using hugepages is non-optimal.