From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 1E73F38308C7 for ; Thu, 8 Dec 2022 12:11:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1E73F38308C7 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670501482; h=from:from:reply-to: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=oFyUWO5gJ/2TtISjJiHUDkEw8NxTWHvqq0bqQj7g32c=; b=KeT9FK/ayxBK2VBpiQS0cXUsXtjP8S9CjNhvz/5+AeCpYk/l+W0/RnM111UuPVv3HtfgB6 +S0DWsxP8hwhu0vRPxwDwYreEjLX+6XIqCLKXe89t5wy2ia/N2Czaa0riXnRBMQDI/AJAI BlFFFcYFk7jGSwN409WsdvexwiVAgBY= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-530-Wk5_6byNNcmIKQA12fHIHw-1; Thu, 08 Dec 2022 07:11:21 -0500 X-MC-Unique: Wk5_6byNNcmIKQA12fHIHw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 069193C10237; Thu, 8 Dec 2022 12:11:21 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.195.114]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B66A11121331; Thu, 8 Dec 2022 12:11:20 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 2B8CBFrt1995844 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 8 Dec 2022 13:11:16 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 2B8CBF7Y1995843; Thu, 8 Dec 2022 13:11:15 +0100 Date: Thu, 8 Dec 2022 13:11:14 +0100 From: Jakub Jelinek To: Andrew Stubbs Cc: gcc-patches@gcc.gnu.org Subject: Re: [PATCH 02/17] libgomp: pinned memory Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham 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 Thu, Jul 07, 2022 at 11:34:33AM +0100, Andrew Stubbs wrote: > > Implement the OpenMP pinned memory trait on Linux hosts using the mlock > syscall. Pinned allocations are performed using mmap, not malloc, to ensure > that they can be unpinned safely when freed. As I said before, I think the pinned memory is too precious to waste it this way, we should handle the -> pinned case through memkind_create_fixed on mmap + mlock area, that way we can create even quite small pinned allocations. Jakub