Chronological Thread 

< Chronological >      < Thread >

---

Hi ,
Thanks for letting me know about the new product analyser.
Regards,
Bindu Sundaresan
1, Residential drive
#264,
Utica, NY-13502
Phone:315-351-3211

From:
discussion-request AT sctp.de
Reply-To:
discussion AT sctp.de
To:
discussion AT sctp.de
Subject: discussion digest, Vol 1 #171 - 5 msgs
Date: Thu, 8 Nov 2001 12:02:04 +0100 (MET)

Send discussion mailing list submissions to

discussion AT sctp.de

To subscribe or unsubscribe via the World Wide Web, visit
http://www.sctp.de/mailman/listinfo/discussion
or, via email, send a message with subject or body 'help' to

discussion-request AT sctp.de

You can reach the person managing the list at

discussion-admin AT sctp.de

When replying, please edit your Subject line so it is more specific
than "Re: Contents of discussion digest..."


Today's Topics:

1. SCTP & ttcp (Florence M Fowler)
2. Re: SCTP & ttcp (Michael Tuexen)
3. SCTP compilation failure on Solaris.
(sunil.raina AT hpsglobal.com)
4. RE: SCTP compilation failure on Solaris. (Tuexen Michael)
5. SCTP implementation and trace (Golan Regev)

--__--__--

Message: 1
Date: Wed, 7 Nov 2001 15:58:52 -0500 (EST)
From: Florence M Fowler
<ffowler AT cs.utk.edu>
To:
discussion AT sctp.de
Subject: [SCTP-Discussion] SCTP & ttcp
Reply-To:
discussion AT sctp.de

We have downloaded your implementation of SCTP and compiled it. My
assignment is to write a ttcp-like application to measure the
thruput of SCTP. I am using the code from ttcp to do the calculations but
obviously I must not know where to put the prep_timer() and read_timer()
functions. I placed the prep_timer()--to begin timing--in the
communicationUpNotif() function and the read_timer() to get the time
elapsed in the shutdownCompleteNotif() function for both transmitter and
receiver. I modeled the receiver after your discard_server and the
transmitter is something like your echo_tool.
Following are the numbers using ttcp:
./ttcp -t -s 160.91.192.149
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ->
160.91.192.149
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 1.85 real seconds = 69.24 Mbit/sec +++
ttcp-t: 16777216 bytes in 0.05 CPU seconds = 2560.00 Mbit/cpu sec
ttcp-t: 2048 I/O calls, msec/call = 0.92, calls/sec = 1107.90
ttcp-t: 0.0user 0.0sys 0:01real 2% 0i+0d 0maxrss 0+2pf 0+0csw
ttcp-t: buffer address 0x8050000

./ttcp -r -s -b 200000
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001,
sockbufsize=200000 tcp
ttcp-r: socket
ttcp-r: rcvbuf
ttcp-r: accept from 160.91.192.165
ttcp-r: 16777216 bytes in 1.88 real seconds = 68.19 Mbit/sec +++
ttcp-r: 16777216 bytes in 0.80 CPU seconds = 160.00 Mbit/cpu sec
ttcp-r: 11210 I/O calls, msec/call = 0.17, calls/sec = 5971.92
ttcp-r: 0.0user 0.7sys 0:01real 42% 0i+0d 0maxrss 0+2pf 0+0csw
ttcp-r: buffer address 0x8050000

Following are the numbers using the SCTP implementation:
./scttcp -t -l 8192 -n 2048 -d 160.91.192.149 -s 160.91.192.165
sctp-t: 16777216 bytes in 44.03 real seconds = 2.91 Mbit/sec +++
sctp-t: 2048 I/O calls, msec/call = 22.01, calls/sec = 46.52

./scttcp -r -s 160.91.192.149
sctp-r: 16777216 bytes in 44.03 real seconds = 2.91 Mbit/sec +++
sctp-r: 2048 I/O calls, msec/call = 22.01, calls/sec = 46.52

Also, we were wondering how we might change/increase the socket buffer
sizes and the window sizes? I am not sure exactly how raw sockets act in
this regard. The SCTP implementation starts out fine but then more
than half-way thru it slows way down and begins to creep along. I just
want to make sure I am measuring things fairly and accurately.

Thank you.

Florence M Fowler



--__--__--

Message: 2
Date: Wed, 7 Nov 2001 22:42:46 +0100
Subject: Re: [SCTP-Discussion] SCTP & ttcp
From: Michael Tuexen
<Michael.Tuexen AT micmac.franken.de>
To:
discussion AT sctp.de
Reply-To:
discussion AT sctp.de

Dear all,

see my comments below.

Best regards
Michael

On Wednesday, November 7, 2001, at 09:58 Uhr, Florence M Fowler wrote:

> We have downloaded your implementation of SCTP and compiled it. My
> assignment is to write a ttcp-like application to measure the
> thruput of SCTP. I am using the code from ttcp to do the calculations
> but
> obviously I must not know where to put the prep_timer() and read_timer()
> functions. I placed the prep_timer()--to begin timing--in the
> communicationUpNotif() function and the read_timer() to get the time
> elapsed in the shutdownCompleteNotif() function for both transmitter and
> receiver. I modeled the receiver after your discard_server and the
> transmitter is something like your echo_tool.
>
The echo_tool does provide some sort of this functionality. Use the
-M option.
> Following are the numbers using ttcp:
> /ttcp -t -s 160.91.192.149
> ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ->
> 160.91.192.149
> ttcp-t: socket
> ttcp-t: connect
> ttcp-t: 16777216 bytes in 1.85 real seconds = 69.24 Mbit/sec +++
> ttcp-t: 16777216 bytes in 0.05 CPU seconds = 2560.00 Mbit/cpu sec
> ttcp-t: 2048 I/O calls, msec/call = 0.92, calls/sec = 1107.90
> ttcp-t: 0.0user 0.0sys 0:01real 2% 0i+0d 0maxrss 0+2pf 0+0csw
> ttcp-t: buffer address 0x8050000
>
> ./ttcp -r -s -b 200000
> ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001,
> sockbufsize=200000 tcp
> ttcp-r: socket
> ttcp-r: rcvbuf
> ttcp-r: accept from 160.91.192.165
> ttcp-r: 16777216 bytes in 1.88 real seconds = 68.19 Mbit/sec +++
> ttcp-r: 16777216 bytes in 0.80 CPU seconds = 160.00 Mbit/cpu sec
> ttcp-r: 11210 I/O calls, msec/call = 0.17, calls/sec = 5971.92
> ttcp-r: 0.0user 0.7sys 0:01real 42% 0i+0d 0maxrss 0+2pf 0+0csw
> ttcp-r: buffer address 0x8050000
>
> Following are the numbers using the SCTP implementation:
> /scttcp -t -l 8192 -n 2048 -d 160.91.192.149 -s 160.91.192.165
> sctp-t: 16777216 bytes in 44.03 real seconds = 2.91 Mbit/sec +++
> sctp-t: 2048 I/O calls, msec/call = 22.01, calls/sec = 46.52
>
> ./scttcp -r -s 160.91.192.149
> sctp-r: 16777216 bytes in 44.03 real seconds = 2.91 Mbit/sec +++
> sctp-r: 2048 I/O calls, msec/call = 22.01, calls/sec = 46.52
>
> Also, we were wondering how we might change/increase the socket buffer
> sizes and the window sizes? I am not sure exactly how raw sockets act
> in
> this regard. The SCTP implementation starts out fine but then more
> than half-way thru it slows way down and begins to creep along. I just
> want to make sure I am measuring things fairly and accurately.
>
In pre14 is a bug which results in this slowdown. It will be fixed in
pre15. In general, you should try to monitor the CPU usage and the link
usage to see what the limiting resource is. Tests with the current code
(which will be published as pre15) saturated a 100MBit link. If neither
the CPU nor the link
is the limiting factor, you should inject more packets and/or increase
the buffer
size for raw sockets. On FreeBSD you can do this using, for example
sysctl -w net.inet.raw.recvspace=16000
I do not know how you do this under Linux, but the sctplib will try to
increase
it automatically for you.
But you should note that this is a prototype implementation which was
never and is not optimized for speed. So you can use it to study the
performance of the
protocol but is not fair to extrapolate measurements from this prototype
to
kernel implementations of SCTP.

Best regards
Michael
> Thank you.
>
> Florence M Fowler
>
>
> _______________________________________________
> discussion mailing list
>
discussion AT sctp.de
> http://www.sctp.de/mailman/listinfo/discussion
>
Michael.Tuexen AT micmac.franken.de


--__--__--

Message: 3
From:
sunil.raina AT hpsglobal.com
To:
discussion AT sctp.de
Date: Thu, 8 Nov 2001 14:00:37 +0530
Subject: [SCTP-Discussion] SCTP compilation failure on Solaris.
Reply-To:
discussion AT sctp.de

Hi,

I tried to compile the curent version of sctplib on Solaris i.e.,
sctplib-1.0.0-pre14, which is supposed to run on Solaris as well. But the
"adaptation.c" file is failing because the function "adl_recv_message" tries
to initialize two members of the "msghdr" structure which are defined under
the condition
"#if defined(_XPG4_2) || defined(_KERNEL)" in the
"/usr/include/sys/socket.h" file.
Can somebody help me out. Do I need to define something to get rid of this
problem or my system is lacking something.

Regards
Sunil Raina

--__--__--

Message: 4
From: Tuexen Michael
<Michael.Tuexen AT icn.siemens.de>
To:
"'discussion AT sctp.de'"

<discussion AT sctp.de>
Subject: RE: [SCTP-Discussion] SCTP compilation failure on Solaris.
Date: Thu, 8 Nov 2001 09:40:56 +0100
Reply-To:
discussion AT sctp.de

Hi,
what version of Solaris are you using?
Best regards
Michael

Michael Tuexen Tel.: +49 89 722 47210
Siemens AG Fax: +49 89 722 48212
ICN WN CS SE 5 E-mail:
Michael.Tuexen AT icn.siemens.de

> -----Original Message-----
> From:
sunil.raina AT hpsglobal.com

[SMTP:sunil.raina AT hpsglobal.com]
> Sent: Thursday, November 08, 2001 9:31 AM
> To:
discussion AT sctp.de
> Subject: [SCTP-Discussion] SCTP compilation failure on Solaris.
> Importance: High
>
> Hi,
>
> I tried to compile the curent version of sctplib on Solaris i.e.,
> sctplib-1.0.0-pre14, which is supposed to run on Solaris as well. But the
> "adaptation.c" file is failing because the function "adl_recv_message" tries
> to initialize two members of the "msghdr" structure which are defined under
> the condition
> "#if defined(_XPG4_2) || defined(_KERNEL)" in the
> "/usr/include/sys/socket.h" file.
> Can somebody help me out. Do I need to define something to get rid of this
> problem or my system is lacking something.
>
> Regards
> Sunil Raina
> _______________________________________________
> discussion mailing list
>
discussion AT sctp.de
> http://www.sctp.de/mailman/listinfo/discussion

--__--__--

Message: 5
charset="iso-8859-1"
Date: Thu, 8 Nov 2001 12:34:55 +0200
From: "Golan Regev"
<golanr AT airslide.com>
To:
<discussion AT sctp.de>
Cc:
<sigtran AT standards.nortelnetworks.com>,

<tsvwg AT ietf.org>
Subject: [SCTP-Discussion] SCTP implementation and trace
Reply-To:
discussion AT sctp.de

Hi,

You can find a nice FREE analyzing tool for SCTP&M2PA in link below:

http://www.airslide.com/download_sigtran_analyzer.html

Best Regards

Golan Regev

Airslide Systems - www.airslide.com


-----Original Message-----
From: Michael Tuexen
[mailto:Michael.Tuexen AT micmac.franken.de]
Sent: Saturday, November 03, 2001 8:09 PM
To:
discussion AT sctp.de
Cc:
bindu_sundaresan AT hotmail.com
Subject: Re: [SCTP-Discussion] SCTP implementation and trace


Dear Bindu,

to learn about the packets I would recommend to use the packet tracer
ethereal which is available at www.ethereal.com and which supports
SCTP.

The trace/log files generated by our sctp prototype are more for
debugging the implementation than for understanding the packets or
protocols.

You can use the example programs of our distribution to generate
traces with ethereal.

Best regards
Michael

On Friday, November 2, 2001, at 06:58 Uhr, Bindu Sundaresan wrote:

> Hi,
> I would like to know how i can view a trace file of SCTP in order to=20
> learn more about the packets.
> Please let me know.
> Thanks
> Regards,
> Bindu
>
> Bindu Sundaresan
> 1, Residential drive
> #264,
> Utica, NY-13502
> Phone:315-351-3211
>
>


--__--__--

_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion


End of discussion Digest_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

---

• [SCTP-Discussion] RE: discussion digest, Vol 1 #171 - 5 msgs, sunil . raina, 11/08/2001
  • <Possible follow-up(s)>
  • [SCTP-Discussion] Re: discussion digest, Vol 1 #171 - 5 msgs, Bindu Sundaresan, 11/08/2001

---

Archive powered by MHonArc 2.6.19+.