From: Kristof Provost <kristof@sigsegv.be>
To: ishare <june.tune.sea@gmail.com>
Cc: Aniruddha Bhattacharyya <aniruddha.aot@gmail.com>,
linux-newbie@vger.kernel.org
Subject: Re: seq in tcp protocol
Date: Sun, 24 Mar 2013 13:08:15 +0100 [thread overview]
Message-ID: <20130324120815.GD9539@thebe.jupiter.sigsegv.be> (raw)
In-Reply-To: <20130324115711.GA9706@debian.localdomain>
On 2013-03-24 19:57:11 (+0800), ishare <june.tune.sea@gmail.com> wrote:
>
> How does the sender decide how many packet is needed to transfer one buffer and
> manager the seq orders of them ?
>
http://en.wikipedia.org/wiki/Nagle%27s_algorithm
--
Kristof
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2013-03-24 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 13:30 seq in tcp protocol ishare
2013-03-23 13:31 ` Kristof Provost
2013-03-24 3:29 ` ishare
2013-03-24 9:37 ` Kristof Provost
2013-03-24 10:26 ` Aniruddha Bhattacharyya
2013-03-24 11:57 ` ishare
2013-03-24 12:08 ` Kristof Provost [this message]
2013-03-30 19:17 ` Anatoliy Sivov
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=20130324120815.GD9539@thebe.jupiter.sigsegv.be \
--to=kristof@sigsegv.be \
--cc=aniruddha.aot@gmail.com \
--cc=june.tune.sea@gmail.com \
--cc=linux-newbie@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