Date: Wed, 08 Aug 2012 09:59:23 -0700 From: Sean Bruno <seanbru@yahoo-inc.com> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org> Subject: Re: Time to increase MAX_TASKS? Message-ID: <1344445163.2813.2.camel@powernoodle.corp.yahoo.com> In-Reply-To: <201208080725.24199.jhb@freebsd.org> References: <1342730963.2656.5.camel@powernoodle.corp.yahoo.com> <201208071730.52899.jhb@freebsd.org> <1344382269.18854.22.camel@powernoodle.corp.yahoo.com> <201208080725.24199.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
<snip>
AcpiOsExecute: acpi_task_count(98), acpi_max_tasks(128) max_threads(3)
<snip>
code modified to generate log message:
for (at = NULL, i = 0; i < acpi_max_tasks; i++)
if (atomic_cmpset_int(&acpi_tasks[i].at_flag, ACPI_TASK_FREE,
ACPI_TASK_USED)) {
at = &acpi_tasks[i];
acpi_task_count++;
if (acpi_task_count > 63)
printf("AcpiOsExecute: acpi_task_count(%d),
acpi_max_tasks(%d) max_threads(%d)\n",
acpi_task_count, acpi_max_tasks,
acpi_max_threads);
break;
}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1344445163.2813.2.camel>