OpenVZ Forum


Home » Mailing lists » Devel » [PATCH] usbatm: Update to use the kthread api.
Re: [PATCH] usbatm: Update to use the kthread api. [message #17074 is a reply to message #16994] Fri, 15 December 2006 15:14 Go to previous messageGo to previous message
Alan Stern is currently offline  Alan Stern
Messages: 5
Registered: December 2006
Junior Member
On Fri, 15 Dec 2006, Christoph Hellwig wrote:

> > Are signals the best available mechanism to request that a thread
> > stop that can exit on it's own.
> 
> Defintly not.  signals should be avoided in kernel threads at all
> cost.

I have a driver that spawns a kernel thread (using kthread_create) which 
does I/O by calling vfs_write and vfs_read.  It relies on signals to 
interrupt the I/O activity when necessary.  Maybe this isn't a good way of 
doing things, but I couldn't think of anything better.

Do you have any suggestions?

Alan Stern

P.S.: What is the reason for saying "signals should be avoided in kernel
threads at all cost"?

_______________________________________________
Containers mailing list
Containers@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH] Set a separate lockdep class for neighbour table's proxy_queue
Next Topic: Re: Getting the new RxRPC patches upstream
Goto Forum:
  


Current Time: Sun Aug 03 12:41:43 GMT 2025

Total time taken to generate the page: 1.11903 seconds