Date: Tue, 19 Sep 2006 12:55:32 -0400 From: Erez Zadok <ezk@cs.sunysb.edu> To: Danny Braniss <danny@cs.huji.ac.il> Cc: Erez Zadok <ezk@cs.sunysb.edu>, Christos Zoulas <christos@zoulas.com>, freebsd-amd64@freebsd.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 [resend] Message-ID: <200609191655.k8JGtWRi021001@agora.fsl.cs.sunysb.edu> In-Reply-To: Your message of "Tue, 19 Sep 2006 10:18:56 %2B0300." <E1GPZse-0000Da-Gf@cs1.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <E1GPZse-0000Da-Gf@cs1.cs.huji.ac.il>, Danny Braniss writes: > > Danny, try something simple first like turning off plock use in amd.conf: > > > > plock = no > > > > And let's see if Amd runs w/o trying any plock'ing first. > > > > Erez. > > does it have a command line equivalent? No. Many amd.conf options don't have command-line equivalents: there's just too many amd.conf options. > danny Erez.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609191655.k8JGtWRi021001>