* tcp_recvmesg hang under NET_DMA
@ 2010-03-09 20:44 Steven J. Magnani
0 siblings, 0 replies; only message in thread
From: Steven J. Magnani @ 2010-03-09 20:44 UTC (permalink / raw)
To: netdev; +Cc: linux-kernel, David S. Miller
Hi,
I've run into a case where using NET_DMA seems to cause a PUT to a
modified ftpd to hang. AFAICT this is because the NET_DMA design queues
up lots of memcpy operations, but doesn't issue or wait for them (and
thus free the associated skbs) until it is time for tcp_recvmesg() to
return. In a case where userland requests a large read (as is the case
in my modified ftpd), packet transfer can grind to a halt because so
many packets are buffered up and there is no event that causes them to
be freed.
I can submit a patch that would issue pending memcpys and clean up
completed ones around tcp_recvmsg's call to sk_wait_data(), but first I
wanted to understand the design better. Were there specific reasons for
deferring the async operations so long?
Thanks,
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-03-09 20:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-03-09 20:44 tcp_recvmesg hang under NET_DMA Steven J. Magnani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).