From nobody Fri Nov 26 20:56:19 2021 X-Original-To: current@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 6B8FA18A78BC for ; Fri, 26 Nov 2021 20:56:39 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) (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 4J16VZ41rXz3rR1; Fri, 26 Nov 2021 20:56:38 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f50.google.com with SMTP id z26so12888505iod.10; Fri, 26 Nov 2021 12:56:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gqXXiFRIJ0rKS0OzOp6XwBbi054wDz+Rma7YTk01sg0=; b=vngxq7+NUjyzNGUPTUXadwpeCUfAej2qbR04y0brZ2Nzm/p5ifdl6aah5hnWztELqs 3hwI8KznALTWe8Ycdcj1YKWNbZwy1MY5OcOSzvIH6cKdcYNxl5UcevapOLDcSnj0Lv96 8knZkBqDdqBb/iS8nsOjbVCgNK0UmF1kczRlXH0H8ZqCCCu/q4nSDM5iybezoaG4OuYy JveTx+r0PZUPKJuekeIhqFhpNuk1viTTX9/RE7GOSb0eoW+HKk17X0mUm0E10/q8C1v4 xpIQNGADW91W30KrEknzD3AL1w2dEWFp7+B03IwklLfPB/9wJl3GPiujuI6mqoen4hAs KlJQ== X-Gm-Message-State: AOAM530tjTzLUJIeigFKBR5D5fnji8Uo1/t7ntnT9jjkA92LGB9fB4ZK 2cV3QcqaM44PmB03/xoyow5hual1HIkHs9X678gGZXfl X-Google-Smtp-Source: ABdhPJx4CoPZc0OAXz7XNa0IHu8goIJ6XKDm9uGN3TIv5XrFIJUwjAJBQzWVsVYnlts86YC0FIG9w0fZvO1BtfefRO0= X-Received: by 2002:a5d:818a:: with SMTP id u10mr37383619ion.140.1637960191219; Fri, 26 Nov 2021 12:56:31 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Fri, 26 Nov 2021 15:56:19 -0500 Message-ID: Subject: Re: VDSO on amd64 To: Kurt Jaeger Cc: current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4J16VZ41rXz3rR1 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.50 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [1.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[1.000]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.50:from]; NEURAL_SPAM_LONG(1.00)[1.000]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.50:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Thu, 25 Nov 2021 at 00:36, Kurt Jaeger wrote: > > Eleven years ago Giuseppe Cocomazzi posted this: > > http://lists.freebsd.org/pipermail/freebsd-hackers/2010-April/031553.html > > vdso and shared page patch I see the patch generated a couple of responses on the list when it was posted, including a plan to follow up with a detailed review that appears not to have happened. It's unfortunate, and as a project we definitely have an issue that not all contributions are addressed in a timely manner. One of the goals of the Git working group, and Warner's newer development practices working group, is to make it easier to handle contributions. Of course contributions can be overlooked regardless of whether they're patches on a mailing list, attached to a Bugzilla PR, opened as a Phabricator review, or as a GitHub or Gitlab pull or merge request. There isn't a technical solution that will fully address this, but we can reduce friction as much as possible.