Re: [go-nuts] net.ListenUDP, ListenTCP & new go routine creation

On Mon, Jun 20, 2016 at 8:09 PM, Matt Harden wrote: > OK, wait. You mentioned namespaces. It is definitely not supported in any > way to have different threads or goroutines running in different namespaces > within a single Go process. The Go scheduler can move a goroutine

Re: [go-nuts] net.ListenUDP, ListenTCP & new go routine creation

Nothing about using the network requires new goroutine creation. I wouldn't expect Dial to create new goroutines, except perhaps temporarily during DNS lookup or something. On Mon, Jun 20, 2016 at 6:38 PM Manohar Kumar wrote: > > > On Monday, June 20, 2016 at 9:31:08 AM

Re: [go-nuts] net.ListenUDP, ListenTCP & new go routine creation

On Monday, June 20, 2016 at 9:31:08 AM UTC-7, Ian Lance Taylor wrote: > > On Sat, Jun 18, 2016 at 10:17 PM, Manohar Kumar > wrote: > > > > Is it possible that a net.ListenTCP or ListenUDP call can result in new > go > > routine/OS thread creation ? I guess not all

Re: [go-nuts] net.ListenUDP, ListenTCP & new go routine creation

On Sat, Jun 18, 2016 at 10:17 PM, Manohar Kumar wrote: > > Is it possible that a net.ListenTCP or ListenUDP call can result in new go > routine/OS thread creation ? I guess not all system calls result in a new go > routine (and OS thread if necessary) creation. But

Re: [go-nuts] net.ListenUDP, ListenTCP & new go routine creation

On 21 Jun 2016 12:42 a.m., "Manohar Kumar" wrote: > > I am mainly interested in Linux and have to make these calls in a part of the code where new OS thread creation isn't desirable. Please note that changing that aspect of the design itself is not an option for me. If

[go-nuts] net.ListenUDP, ListenTCP & new go routine creation

Hello, Is it possible that a net.ListenTCP or ListenUDP call can result in new go routine/OS thread creation ? I guess not all system calls result in a new go routine (and OS thread if necessary) creation. But ListenTCP & UDP does many things underneath and its not clear if it can lead to new