From owner-freebsd-current Fri Sep 7 16:24:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E298637B405; Fri, 7 Sep 2001 16:24:46 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f87NOjX34045; Fri, 7 Sep 2001 17:24:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f87NOeh65478; Fri, 7 Sep 2001 17:24:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109072324.f87NOeh65478@harmony.village.org> To: Bruce Evans Subject: Re: RFC: hack volatile bzero and bcopy Cc: John Baldwin , Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Sep 2001 20:55:11 +1000." <20010907203306.J38152-100000@alphplex.bde.org> References: <20010907203306.J38152-100000@alphplex.bde.org> Date: Fri, 07 Sep 2001 17:24:40 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010907203306.J38152-100000@alphplex.bde.org> Bruce Evans writes: : In the case of if_ie.c and bcopy(), bcopy() is not suitable for copying : memory that doesn't behave like RAM. Some optimized versions of it : do out of order and/or repeated copies. This might be very bad for : volatile device memory. I think rewriting if_ie.c to use bus_space : would make most of the warnings go away automatically. Right. bus_space_read/write_N likely should be used instead. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message