From: Stephen Hemminger <shemminger@osdl.org>
To: "Majumder, Rajib" <rajib.majumder@credit-suisse.com>
Cc: "'netdev@vger.kernel.org'" <netdev@vger.kernel.org>
Subject: Re: TCP ACK
Date: Thu, 24 Aug 2006 10:16:42 -0700 [thread overview]
Message-ID: <20060824101642.05f68718@localhost.localdomain> (raw)
In-Reply-To: <F444CAE5E62A714C9F45AA292785BED30EB97453@esng11p33001.sg.csfb.com>
On Thu, 24 Aug 2006 23:03:22 +0800
"Majumder, Rajib" <rajib.majumder@credit-suisse.com> wrote:
> Hi,
>
> I had a fundamental question regarding stack. When does TCP ack a segment? Is it immediately receiving a segment or after copying the data from kernel to user i.e after read() system call returns?
>
> Any input is highly appreciated.
>
> Thanks
>
> Rajib
>
TCP ack's when segment is received and placed in the socket buffer.
For questions like this, you are better off looking at traditional unix
network programming books
http://www.thefreecountry.com/documentation/unixbooks.shtml
--
Stephen Hemminger <shemminger@osdl.org>
All non-trivial abstractions, to some degree, are leaky.
prev parent reply other threads:[~2006-08-24 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 15:03 TCP ACK Majumder, Rajib
2006-08-24 17:16 ` Stephen Hemminger [this message]
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=20060824101642.05f68718@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=rajib.majumder@credit-suisse.com \
/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