Dear all,
we have used a client to do
while (1) {
send(fd, buffer, n);
}
against a discard server on a different machine. The
sender is running FreeBSD 7.1, for the receiver we
used two different machines, one running FreeBSD 7.1
another one Mac OS X 10.5.6. The machines are old,
so I do
>Yoshi,
>I have attached a patch. Let me know if this fixes the problem.
>
>jayanth
>
Jayanth,
thanks for the patch. I tested with it, and the system performs nicely.
I appreciate your help.
Yoshi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of th
* jayanth <[EMAIL PROTECTED]> [010928 14:43] wrote:
> Yoshi,
> I have attached a patch. Let me know if this fixes the problem.
>
> jayanth
cool, but..
> --- tcp_output.c Fri Sep 28 11:15:32 2001
> +++ tcp_output.c.new Fri Sep 28 12:05:03 2001
> @@ -133,7 +133,7 @@
>* If there is s
Yoshi,
I have attached a patch. Let me know if this fixes the problem.
jayanth
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>
> > This issue is a combination of mbuf cluster size and the
> > TF_MORETOCOME flag.
>
> > if (len) {
> > if (len == tp->t_ma
Probably add a new flag TF_IDLE that is true, if there is more data
to send when the connection was idle. This way the next time
around the idle variable will be true if the TF_IDLE flag is true
and if we can empty the socket buffer all the data will be sent.
Will send you a patch soon.
jayanth
> This issue is a combination of mbuf cluster size and the
> TF_MORETOCOME flag.
> if (len) {
> if (len == tp->t_maxseg)
> goto send;
> if (!(tp->t_flags & TF_MORETOCOME) &&
>
I think this is a performance issue and it would be nice to send the 589 bytes
of data immediately rather than wait for the delayed ack from the
other end.
This issue is a combination of mbuf cluster size and the
TF_MORETOCOME flag.
2049 is one byte more than the cluster size, so the first 14
> > >
> > > I tried to say that it had no effect between FreeBSD4.3 and Solaris,
>on my
> > > problem. That's what I did previously.
> > >
> > > I found discussion on "delayed ack problem"(January 24 and 25) in
>this
> > > m
> >
> > I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my
> > problem. That's what I did previously.
> >
> > I found discussion on "delayed ack problem"(January 24 and 25) in this
> > mailing list. Though still do not understand why del
On Tue, 25 Sep 2001 [EMAIL PROTECTED] wrote:
> Sorry, it seems it works between two FreeBSD machines.
>
> I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my
> problem. That's what I did previously.
>
> I found discussion on "delayed ack problem"(January 24 and 25) in thi
> On Fri, 21 Sep 2001, Tsuchiya Yoshihiro wrote:
>
> > Mike Silbersack wrote:
> >
> > >Try disabling delayed ACKs and see how that affects your results. The
> > >default delay for delayed acks is 100ms.
> > >
> > >sysctl -w net.inet.tcp.delayed_ack=0
>
On Fri, 21 Sep 2001, Tsuchiya Yoshihiro wrote:
> Mike Silbersack wrote:
>
> >Try disabling delayed ACKs and see how that affects your results. The
> >default delay for delayed acks is 100ms.
> >
> >sysctl -w net.inet.tcp.delayed_ack=0
> >
>
> I found a machine with FreeBSD4.3 and tried it, but
Just tried it on a 4.4-RELEASE box and it appears to work :)
* -Original Message-
* From: [EMAIL PROTECTED]
* [mailto:[EMAIL PROTECTED]]On Behalf Of Tsuchiya Yoshihiro
* Sent: Friday, September 21, 2001 1:28 AM
* To: Mike Silbersack
* Cc: [EMAIL PROTECTED]
* Subject: Re: TCP performance
Mike Silbersack wrote:
>On Fri, 21 Sep 2001 [EMAIL PROTECTED] wrote:
>
>>and we changed the size from 1 to 1 byte and measured the time of
>>read/write pair on the server. Usually the measured time is
>>around or less than 1 msec, however it is always 100msec when the size is
>>between 2049
On Fri, 21 Sep 2001 [EMAIL PROTECTED] wrote:
> and we changed the size from 1 to 1 byte and measured the time of
> read/write pair on the server. Usually the measured time is
> around or less than 1 msec, however it is always 100msec when the size is
> between 2049 and 2919 byte or between
Hello,
we observed that TCP is somewhat slow with FreeBSD.
Does anybody know this kind of behavior?:
We have investigated the problem with simple program like:
client server
for(){ for(){
write(fd, buf, size); read (fd, buf, size);
16 matches
Mail list logo
