From owner-freebsd-hackers@freebsd.org Sun Dec 13 19:21:02 2020 Return-Path: Delivered-To: freebsd-hackers@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 29D3B4C1518 for ; Sun, 13 Dec 2020 19:21:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvDrt06g1z4n19; Sun, 13 Dec 2020 19:21:01 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f173.google.com with SMTP id q25so16743657oij.10; Sun, 13 Dec 2020 11:21:01 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wEBRKarIyIxXJe3U9Srfi+yO4ylyn+7S/LGn9RFpFjw=; b=TK6Paj+Cm260TsETMK/dW+jbPQ+HOPGNY8laGvdVpKf8iOxM4kTBcVq2FI/wjZsbv1 PUj92sD2lz5XQExUha0C1gyQ+xjXyMnstTWVEIwaX1Mzd2XB/77HXEQYHF7+mQJTBYj+ AnFtIfQNgm7+xTbytWtkHwhX0Efc3RT9OuWdYY4B/IbDU/natI+hEaO1YsEch1vagsie 3TnF4ctLkfTrTBN8qZi9br1mYkoOipbgtnGnsQVXkuDNtbXZkeKwErsJnJLcXnVrTEKs ZDwtM5QKczv17uwuh0ubck/jeDpSZhvsVBD4DoSgJnwfAgRNl1ePAaR4JprIvV1/SeQk 2h2w== X-Gm-Message-State: AOAM531Bn2H6dihZzMY1sAEiuz1GpvDxLqIUpCvkIgOGaEaeUVB8Ibkt VAWYDQaABgn4fOYBSsrkEd7+JHOHNJ9kC2LWwon6IcXEdW0= X-Google-Smtp-Source: ABdhPJyChzJHZN/g9YwAFw+Ne15bBnnUaEEePSsjTqeux/e2syu0loUGb4qu3gv9M4WjrEi6FKVY1zQVmYut/viL8j4= X-Received: by 2002:aca:dd09:: with SMTP id u9mr15523427oig.73.1607887260859; Sun, 13 Dec 2020 11:21:00 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Alan Somers Date: Sun, 13 Dec 2020 12:20:49 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Warner Losh Cc: Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvDrt06g1z4n19 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 19:21:02 -0000 On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: > > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: >> > I'm trying to exercise the aio code that handles character devices >> > that >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there any >> > remaining character devices that don't allow unmapped I/O? >> > >> > -Alan >> > >> >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, >> flash/mx25l. >> > Hm. I don't have any of those. > > There are times that it's disabled administratively as well, but that may > be on a per-I/O basis. > vfs.zfs.vol.unmap_enabled: 1 > This one doesn't seem to work. It looks like the only functionality it gates these days is DIOCGDELETE. > vfs.unmapped_buf_allowed: 1 > Well, this one works. Thanks for the tip. Unfortunately, it's a tunable, so I can't use it for any kind of automated testing. > > "Why do you ask?" is the next question... > > Warner >