Time to increase MAX_TASKS?

[Moore, Robert]

Just FYI, we've seen the AcpiOsExecute task Q get very large if
There is a GPE flood that results in many, many notify operations.

And in these cases, it was always related to the EC (Embedded Controller).

Bob


> -----Original Message-----
> From: owner-freebsd-acpi at freebsd.org [mailto:owner-freebsd-
> acpi at freebsd.org] On Behalf Of Sean Bruno
> Sent: Wednesday, August 08, 2012 9:59 AM
> To: John Baldwin
> Cc: freebsd-acpi at freebsd.org
> Subject: Re: Time to increase MAX_TASKS?
> 
> 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;
>         }
> 
> _______________________________________________
> freebsd-acpi at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe at freebsd.org"