From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCHv9] vhost: experimental tx zero-copy support Date: Mon, 18 Jul 2011 10:16:06 +0300 Message-ID: <20110718071606.GA29538@redhat.com> References: <20110717193540.GA29392@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Jesper Juhl Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Sun, Jul 17, 2011 at 10:01:41PM +0200, Jesper Juhl wrote: > > @@ -28,10 +29,18 @@ > > > > #include "vhost.h" > > > > +static int zcopytx; > > +module_param(zcopytx, int, 0444); > > Should everyone be able to read this? How about "0440" just to be > paranoid? or? I find it very helpful to have the parameter visible in sysfs. Given that: [mst@tuck linux-2.6]$ grep module_param drivers/net/*c|grep [64]44|wc -l 14 [mst@tuck linux-2.6]$ grep module_param drivers/net/*c|grep [64]40|wc -l 0 [mst@tuck linux-2.6]$ grep module_param drivers/net/*c|grep [64]00|wc -l 7 So at least the precedent is against 0440. What do you think? -- MST