|
Bugzilla – Full Text Bug Listing |
| Summary: | setting UnixSocketFd socket buffer size | ||
|---|---|---|---|
| Product: | dce | Reporter: | Tom Henderson <tomh> |
| Component: | other | Assignee: | Hajime Tazaki <tazaki> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Hardware: | PC | ||
| OS: | Linux | ||
I think it can be removed. I fixed with the changeset. http://code.nsnam.org/ns-3-dce/rev/bfc53812adec |
in the UnixSocketFd constructor, there are two statements: m_socket->SetAttributeFailSafe ("SndBufSize", UintegerValue (126976)); m_socket->SetAttributeFailSafe ("RcvBufSize", UintegerValue (126976)); that were added by Frederic in changeset: changeset: 150:74b78e814bfd user: frederic.urbani@inria.fr date: Mon Sep 12 14:20:52 2011 +0200 summary: Change socket buffer size to value more like in Linux Manual Pages. However, when using e.g. iperf over an ns-3 TCP socket, for instance, this has the effect of later overwriting the value for RcvBufSize and SndBufSize on the socket (after the ns-3 attribute setter takes effect). For ns-3 at least, these are not needed, since the default buffer sizes are very close to these values (131K). So in my TCP testing, I have been commenting these out in my DCE. Can they be deleted altogether, or are there socket types where these are still needed?