From: rahul b jain cs student <rbj2@oak.njit.edu>
To: Thomas Giese <Thomas.giese@tgsoftware.de>
Cc: Kernel Traffic Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Turning off TCP Delayed acks
Date: Wed, 21 Jul 2004 18:58:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0407211854530.6744@chrome.njit.edu> (raw)
In-Reply-To: <007c01c46f47$af32f510$2f8afea9@tgsiemens>
Mr. Giese,
Thank you for your response.
As you wrote TCP_NODELAY is used to turn off Nagle. As per theory this
algo will be running at the sender side and delay acks at the reciever
side. If I turn off Nagel at sender side, wont this lead to the silly
window syndrome ??
Also is it true that Nagles algo and hence delay acks come into play only
if the packet size is small ??
Thanks,
Rahul.
On Wed, 21 Jul 2004, Thomas Giese wrote:
>
> Nagle is automatically turned off on a per socket basis if you set the
> TCP_NODELAY
> socket option on the socket. Turning nagle off globally is a bit drastic in
> most cases.
>
> Thomas Giese
>
> ----- Original Message -----
> From: "rahul b jain cs student" <rbj2@oak.njit.edu>
> Newsgroups: linux.kernel
> Sent: Wednesday, July 21, 2004 6:30 PM
> Subject: Turning off TCP Delayed acks
>
>
> > Hi everyone,
> >
> > For an experiment, I wanted to turn off the delayed ack system in the
> > kernel so that there is an ack for each and every packet sent by the
> > source. Can anyone give me some ideas on how to go about doing this.
> >
> >
> > Thanks,
> > Rahul.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
next parent reply other threads:[~2004-07-21 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ks8W-2RR-51@gated-at.bofh.it>
[not found] ` <007c01c46f47$af32f510$2f8afea9@tgsiemens>
2004-07-21 22:58 ` rahul b jain cs student [this message]
2004-07-21 16:18 rahul b jain cs student
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.58.0407211854530.6744@chrome.njit.edu \
--to=rbj2@oak.njit.edu \
--cc=Thomas.giese@tgsoftware.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®