From nobody Tue Jun 27 13:47:05 2023 X-Original-To: dev-commits-src-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Qr5cD0462z4jrPW; Tue, 27 Jun 2023 13:47:08 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oa1-x35.google.com (mail-oa1-x35.google.com [IPv6:2001:4860:4864:20::35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Qr5cC5Pz5z4Dn0; Tue, 27 Jun 2023 13:47:07 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-1b0627731d1so508957fac.1; Tue, 27 Jun 2023 06:47:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687873626; x=1690465626; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2CyGkG3JRY3SZfdVrl7ii7mTJPKvbGgtVGnCe4+Dj+g=; b=FwZdQQINnyOH3bMxxYcZ1V+mAuPqXEqyS2H7FQSSpwf54QBkbAADSahkuO/Nek+E/A JXmHf8asDWdLCI8FfB9XmdADPXMiUOcLCLlB/FRIEd61otzVEXGKyhjaJO5TsXWMd5Xz 5e463KnNHhNKHE/j/bFIMr+hqBbt7VfhxS2t+JA2bJJV7Zr9Qwt45imUJNvlRLOvKqxC R55aeOuJsubcaA7poATYtMMuyZjCLTGM74SWlj8nsNGs3QyYTKOuhzJ+lF4SMmbcwrRH O3QjJ9K8qJP9soiny6vNPrDe9TUOn71feu0WQ9eS3MPEbSk3z6QfbyGXmn2bj+ydkul6 koMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687873626; x=1690465626; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2CyGkG3JRY3SZfdVrl7ii7mTJPKvbGgtVGnCe4+Dj+g=; b=HMMrrmchILhaay5FUJek1mlzHDIDWk/RhYso9Q1Fd1dSh4McuuBnrK0E3zALv07dm2 eRyz54caX+fAWxkDsPvWui2llNa+CFrb4Yo488xG+jHluvaIFy7MVrYefCX4f2AQ/PH4 I7mrEig4ulVvUWl8bjbKbFLMrjpNZ2XHgrzbRJqEFH4JixfThCOT6J0RhKewBCl/uZD+ Ap9k8VzVfQ9elScV1dTU52EnVzAi/xr5KM/O5dyfQK3a1b15bnceUMeCZ+i+8WP3Ekg3 KBsBHE/gJywdBnkAAIZbbnLwJLhJn4bEanC68NvgqW1V5v+V5aTqeIO4uzKww5TIvcW4 4d7Q== X-Gm-Message-State: AC+VfDyxLJ5w8HUzfA695bP1O/2wRG6/QKuFvHLuVuihoo9dBtdscoGp ndBF57+ASeO5J3qDI8aUL9YWfYY8Zyzj79G4L4sLJLQo X-Google-Smtp-Source: ACHHUZ57ZkJN3lSill1+wZqYBBtMVL6qXqwPPynJw85abJdFt1DMU+rc6Xc3NyHfbT91V9F/KeI5i2YFEt0UgJ+J2Xc= X-Received: by 2002:a05:6870:5383:b0:1a6:5f0d:f955 with SMTP id h3-20020a056870538300b001a65f0df955mr21219770oan.1.1687873626020; Tue, 27 Jun 2023 06:47:06 -0700 (PDT) List-Id: Commit messages for all branches of the src repository List-Archive: https://lists.freebsd.org/archives/dev-commits-src-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-src-all@freebsd.org X-BeenThere: dev-commits-src-all@freebsd.org MIME-Version: 1.0 Received: by 2002:a8a:611:0:b0:4e1:6042:cdc9 with HTTP; Tue, 27 Jun 2023 06:47:05 -0700 (PDT) In-Reply-To: References: <202306271156.35RButXO071800@gitrepo.freebsd.org> From: Mateusz Guzik Date: Tue, 27 Jun 2023 15:47:05 +0200 Message-ID: Subject: Re: git: a6c0d801ca59 - main - libpthread: allocate rwlocks and spinlocks in dedicated cachelines To: Konstantin Belousov Cc: src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Qr5cC5Pz5z4Dn0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 6/27/23, Konstantin Belousov wrote: > On Tue, Jun 27, 2023 at 11:56:55AM +0000, Mateusz Guzik wrote: >> The branch main has been updated by mjg: >> >> URL: >> https://cgit.FreeBSD.org/src/commit/?id=a6c0d801ca5934bb9b9cca6870ea7406d5db0641 >> >> commit a6c0d801ca5934bb9b9cca6870ea7406d5db0641 >> Author: Greg Becker >> AuthorDate: 2023-06-27 01:08:29 +0000 >> Commit: Mateusz Guzik >> CommitDate: 2023-06-27 11:56:44 +0000 >> >> libpthread: allocate rwlocks and spinlocks in dedicated cachelines > Why e.g. mutexes were not handled in the similar way? > Sorting out the general problem looks like quite a bit of churn. For example the aforementioned mutexes end up with __thr_calloc -> __crt_calloc which does not provide alignment support afaics. The above patch sorts out some of the problem in a trivial manner, so I saw no issue putting it in. -- Mateusz Guzik