Re: WSAENOBUFS on winsock client application
- From: Len Holgate <len.holgate@xxxxxxxxxxx>
- Date: Fri, 9 May 2008 08:11:01 -0700 (PDT)
Your ideas make sense. I also was thinking about this weird fact, but then I
did an assumption, that a call to WSARecv on given thread just reaches
memory limit for a given process, but the rest requests (on different
thread/connections) goes well because they consume less memory.
I see where you're coming from...
In user mode 90 % of all errors 'WSAENOBUFS' are arised just because simple
memory allocation fails. But I think if request goes to appropriate protocol
provider (say, \Device\Tcp) and provider is unable to allocate non-paged
pool memory the same error is passed to user mode.
A pity that we can't differentiate between the two kinds :(
Len Holgate
http://www.lenholgate.com
Free C++ IOCP server framework available here: http://www.lenholgate.com/archives/000637.html
.
- References:
- WSAENOBUFS on winsock client application
- From: FriedhelmEichin
- Re: WSAENOBUFS on winsock client application
- From: Volodymyr M. Shcherbyna
- Re: WSAENOBUFS on winsock client application
- From: FriedhelmEichin
- Re: WSAENOBUFS on winsock client application
- From: Volodymyr M. Shcherbyna
- Re: WSAENOBUFS on winsock client application
- From: Len Holgate
- Re: WSAENOBUFS on winsock client application
- From: Volodymyr M. Shcherbyna
- WSAENOBUFS on winsock client application
- Prev by Date: Re: WSAENOBUFS on winsock client application
- Next by Date: Re: WSAENOBUFS on winsock client application
- Previous by thread: Re: WSAENOBUFS on winsock client application
- Next by thread: Re: WSAENOBUFS on winsock client application
- Index(es):
Relevant Pages
|
|