[Ns-bugs] [Bug 1006] UDP socket tx buffer back pressure needed
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Mon Dec 12 20:00:22 PST 2011
https://www.nsnam.org/bugzilla/show_bug.cgi?id=1006
Adrian S.-W. Tam <adrian.sw.tam at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |adrian.sw.tam at gmail.com
AssignedTo|ns-bugs at isi.edu |adrian.sw.tam at gmail.com
Severity|normal |enhancement
--- Comment #1 from Adrian S.-W. Tam <adrian.sw.tam at gmail.com> 2011-12-12 23:00:21 EST ---
I did exactly the same thing in a previous research project (modification was
done in ns-3.4). The current ns-3 model is a "non-blocking" socket, which the
send call will succeed anyway. But I think many real-world application expects
a blocking socket, which does not return the call until the lower layer can
really take the data.
Doing this will add a boolean m_blocking variable to ns3::Socket, so when
m_blocking==false, the current code is run, but when m_blocking==true, we need
to return immediately doing nothing for the Send call and invoke a callback
when the socket becomes available again.
Let me take up this as an enhancement, but since it is near code freeze time, I
will wait until the release to commit the code.
--
Configure bugmail: https://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Ns-bugs
mailing list