From owner-freebsd-arch@freebsd.org Sat Nov 30 20:46:59 2019 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 49EB11B7A6B for ; Sat, 30 Nov 2019 20:46:59 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 47QNhz021mz4VGb for ; Sat, 30 Nov 2019 20:46:59 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id F34C31B7A6A; Sat, 30 Nov 2019 20:46:58 +0000 (UTC) Delivered-To: arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F1FD91B7A69 for ; Sat, 30 Nov 2019 20:46:58 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi1-f171.google.com (mail-oi1-f171.google.com [209.85.167.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47QNhy1LhNz4VGZ for ; Sat, 30 Nov 2019 20:46:57 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi1-f171.google.com with SMTP id o12so28934904oic.9 for ; Sat, 30 Nov 2019 12:46:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to:content-transfer-encoding; bh=y0pFjh7DdSUF9Tl3hwVXRh57T/JQ3vJ6U3cDHrIshDI=; b=Sk5QAvkpUsox/0M7Nkzr/Dq5uvlhzHrTT4cfRRDHStv8hmSbzkCeb4JtswIdnCOJqW hfu5OaB8yYCthkRTozDko/4xq6zccmeQKVxzch8NYB29nm1fsNtK8ada2UaBlwfOBUr6 VnWtQZ+95AE9+WY3LFNMbhEryW6ee5Kpr8GwAHnSrwnD7pzQMLh8XPcYmvUqMp55AbOB Ymn4V9SA+G2vSomcj1PRbrh6sUf0qPO0Qm7StYwfSNfNDvO9y66f306Dq0rpmKBoB6GO HYxqEkVb94hJGW8f/nLIrV6Yn85Cxe4YlVNOSwXpwAqKgJprmPMBb5mUOeKw3jDPBIDy FK/Q== X-Gm-Message-State: APjAAAVEti1QglssgMsnx+RxqZPOO7iW5oCzAm2g/eTCdc5eodQ84zGJ W01DDI8ctfD8l//Ts381dl0ADWgy X-Google-Smtp-Source: APXvYqxMVTncAbMw6ADCFhnTIzEp+3/MuP0FLnYpP4JKvv9SQYRF/Y6+eqaphwdCuc+LCzEHHJmHZA== X-Received: by 2002:a05:6808:9a2:: with SMTP id e2mr16416236oig.123.1575146816690; Sat, 30 Nov 2019 12:46:56 -0800 (PST) Received: from mail-oi1-f181.google.com (mail-oi1-f181.google.com. [209.85.167.181]) by smtp.gmail.com with ESMTPSA id x189sm4098387oig.20.2019.11.30.12.46.56 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 30 Nov 2019 12:46:56 -0800 (PST) Received: by mail-oi1-f181.google.com with SMTP id 128so20915392oih.4 for ; Sat, 30 Nov 2019 12:46:56 -0800 (PST) X-Received: by 2002:aca:6006:: with SMTP id u6mr18076831oib.137.1575146816198; Sat, 30 Nov 2019 12:46:56 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org From: Conrad Meyer Date: Sat, 30 Nov 2019 12:46:45 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Killing RANDOM_LOADABLE? To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47QNhy1LhNz4VGZ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of csecem@gmail.com designates 209.85.167.171 as permitted sender) smtp.mailfrom=csecem@gmail.com X-Spamd-Result: default: False [-2.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[cem@freebsd.org]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; FORGED_SENDER(0.30)[cem@freebsd.org,csecem@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[cem@freebsd.org,csecem@gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[arch@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[171.167.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.34)[ip: (-1.53), ipnet: 209.85.128.0/17(-3.16), asn: 15169(-1.94), country: US(-0.05)]; RWL_MAILSPIKE_POSSIBLE(0.00)[171.167.85.209.rep.mailspike.net : 127.0.0.17]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Nov 2019 20:46:59 -0000 Hi, If you use / need RANDOM_LOADABLE, can you provide some information on your use case and needs? If RANDOM_LOADABLE support was dropped in FreeBSD, what would prevent you from carrying a local patch to redirect the same APIs in your downstream source tree, where you already carry some proprietary random device implementation? This option creates significant complexity in the random device. There are some simplifications we can make without removing the option, but there are tradeoffs, and removing the option is by far the most straightforward course. If you do not have a use for RANDOM_LOADABLE but know someone not subscribed to arch who might, I'd appreciate it if you could forward this to their attention. I'd prefer to avoid a discussion of imaginary or hypothetical use cases by non-consumers =E2=80=94 I'm looking = for real consumers' needs. Thanks, Conrad