Re: [patch] Threads performance - allow signal handler to not call handler

• Next message: Alan Cox: "Re: IDE and hot-swap disk caddies"
• Previous message: Corey Minyard: "[patch] Threads performance - allow signal handler to not call handler"
• In reply to: Corey Minyard: "[patch] Threads performance - allow signal handler to not call handler"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

minyard@acm.org said:
> With this patch, if the flag is set, the signal handler won't get
> called (thus saving the overhead of going in and out of userland for
> the handler), but it will still wake up sigsuspend() and select().

I've wanted this for UML as well. I have some empty signal handlers which
exist for no reason other than to wake up pause/sigsuspend/et al.

                                Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Alan Cox: "Re: IDE and hot-swap disk caddies"
• Previous message: Corey Minyard: "[patch] Threads performance - allow signal handler to not call handler"
• In reply to: Corey Minyard: "[patch] Threads performance - allow signal handler to not call handler"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Mar 31 2002 - 22:00:14 EST