Date: Mon, 13 Aug 2012 11:27:18 -0400 From: John Baldwin <jhb@freebsd.org> To: Sean Bruno <seanbru@yahoo-inc.com> Cc: "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org> Subject: Re: Time to increase MAX_TASKS? Message-ID: <201208131127.18457.jhb@freebsd.org> In-Reply-To: <1344445163.2813.2.camel@powernoodle.corp.yahoo.com> References: <1342730963.2656.5.camel@powernoodle.corp.yahoo.com> <201208080725.24199.jhb@freebsd.org> <1344445163.2813.2.camel@powernoodle.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, August 08, 2012 12:59:23 pm Sean Bruno wrote: > On Wed, 2012-08-08 at 04:25 -0700, John Baldwin wrote: > > I meant that with the limit jacked up to something that silences the > > warning > > (such as 128), what is the max number of tasks queued? > > > > > > I set debug.acpi.max_tasks=128 and added a temp log message to > acpi_task_enqueue(). I see the system request *98* tasks according to > my test on this new Dell box. Is it possible that the queue really > isn't running yet or something? Yes, it isn't running during the first pass of probe and attach. It would be good to know what the source of tasks besides acpi_cpuX devices was. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208131127.18457.jhb>