[Bug 1001629] New: bsd stack uses wrong timeout values if hz != 100

[bugzilla-daemon@bugs.ecos.sourceware.org]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001629

           Summary: bsd stack uses wrong timeout values if hz != 100
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: normal
         Component: TCP/IP
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: bernd.edlinger@hotmail.de
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Created an attachment (id=1842)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1842)
proposed patch to solve this defect

if the eCos kernel is configured to 1000 IRQ/s all timeouts in the bsd_tcpip
stack expire in 1/10th of the expected time.

For instance all timeouts given with setsockopt(SOL_SOCKET, SO_RCVTIMEO),
which has a potential to break existing TCP/IP applications.

The reason is the wrong assumption that hz is always 100 in the file
"ecos/packages/net/bsd_tcpip/current/src/ecos/support.c".

Attached is a proposed patch to fix this issue
and a similar problem in show_ticks_in_us(),
where it is taken for granted, that the NOMINATOR in
CYGNUM_KERNEL_COUNTERS_RTC_RESOLUTION is always 1000000000 (1E9)
which is also not true in general.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.