From owner-svn-src-all@FreeBSD.ORG Wed Jan 18 18:49:07 2012 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1F2E106566B; Wed, 18 Jan 2012 18:49:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 890FF8FC08; Wed, 18 Jan 2012 18:49:07 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 2295046B06; Wed, 18 Jan 2012 13:49:07 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A53F2B968; Wed, 18 Jan 2012 13:49:06 -0500 (EST) From: John Baldwin To: Pyun YongHyeon Date: Wed, 18 Jan 2012 09:53:51 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201172215.q0HMFXgI009891@svn.freebsd.org> In-Reply-To: <201201172215.q0HMFXgI009891@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201201180953.51362.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 18 Jan 2012 13:49:06 -0500 (EST) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r230286 - head/sys/dev/bge X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2012 18:49:07 -0000 On Tuesday, January 17, 2012 5:15:33 pm Pyun YongHyeon wrote: > Author: yongari > Date: Tue Jan 17 22:15:33 2012 > New Revision: 230286 > URL: http://svn.freebsd.org/changeset/base/230286 > > Log: > Introduce a tunable that disables use of MSI. > Non-zero value will use INTx. Hmm, do you think it is best to do this on a per-device level vs a per-driver level (e.g. a 'hw..msi' tunable ala mfi(4))? Also, I think it is better to have a flag whose value more closely matches enable/disable (so 1 for enable, etc.) and default it to on, than to have a 'disable' tunable. -- John Baldwin