From owner-freebsd-arm@freebsd.org Thu Jul 18 13:50:25 2019 Return-Path: Delivered-To: freebsd-arm@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 3E1ACA92B4 for ; Thu, 18 Jul 2019 13:50:25 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail.myserver.ws (mail.myserver.ws [144.217.111.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.myserver.ws", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 967998A114 for ; Thu, 18 Jul 2019 13:50:24 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from eldorado (50-243-135-133-static.hfc.comcastbusiness.net [50.243.135.133]) (Authenticated sender: sm@ara-ler.com) by mail.myserver.ws (Postfix) with ESMTPSA id DCF7AA3EDA; Thu, 18 Jul 2019 13:50:12 +0000 (UTC) Date: Thu, 18 Jul 2019 07:50:09 -0600 From: Sergey Manucharian To: Oleksandr Tymoshenko , freebsd-arm@freebsd.org Subject: Re: Writing to /dev/fb0 Message-ID: <20190718135009.GX2903@eldorado> References: <20190621170845.GD2903@eldorado> <20190621171343.GE2903@eldorado> <20190621190502.GA35692@bluezbox.com> <20190621193419.GG2903@eldorado> <20190624213339.GM2903@eldorado> <20190718131525.GJ2342@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190718131525.GJ2342@funkthat.com> User-Agent: Mutt/1.12.0 (2019-05-25) X-Rspamd-Queue-Id: 967998A114 X-Spamd-Bar: ++++++ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 144.217.111.45 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [6.13 / 15.00]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(3.00)[133.135.243.50.zen.spamhaus.org : 127.0.0.4]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(0.00)[+a:mail.myserver.ws]; NEURAL_SPAM_SHORT(0.63)[0.626,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[ara-ler.com]; NEURAL_SPAM_MEDIUM(0.95)[0.954,0]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mail.myserver.ws]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(1.00)[1.000,0]; IP_SCORE(0.06)[ipnet: 144.217.0.0/16(-0.85), asn: 16276(1.17), country: FR(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:16276, ipnet:144.217.0.0/16, country:FR]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Spam: Yes X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2019 13:50:25 -0000 Excerpts from John-Mark Gurney's message from Thu 18-Jul-19 06:15: > > As I already mentioned, these messages > > > > WARNING: Device driver fb has set "memattr" inconsistently (drv 0 pmap 3). > > > > flood console. So, the actual performance is very poor because of that, > > Looks like those messages need to be rate limited... There's > counter_ratecheck and ratecheck functions that can be used to easily > fix this.. That sounds good, but shouldn't this be fixed in the fb driver to "set memattr consistently"? -- Thanks, Ϟϻ