From: kuznet@ms2.inr.ac.ru
To: kalele@veritas.COM (Shirish Kalele)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [NFS] NFSD over TCP: TCP broken?
Date: Wed, 17 Oct 2001 21:58:37 +0400 (MSK DST) [thread overview]
Message-ID: <200110171758.VAA22159@ms2.inr.ac.ru> (raw)
In-Reply-To: <023a01c15708$a275d270$3291b40a@fserv2000.net> from "Shirish Kalele" at Oct 17, 1 04:45:00 am
Hello!
> where the interleaving gets in.
I do not think that you diagnosed the problem correctly.
nfsd used non blocking io and write to tcp is strictly atomic in this case.
> I'm not sure if TCP should be handling this
> or NFSD. From what little I know, TCP should serialize requests it gets and
> atomically write them out,
However, it does not and it should not. Like concurrent write()
to any other file, the result is unpredictably interleaved data.
Alexey
next prev parent reply other threads:[~2001-10-17 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00f501c156f9$95337ef0$3291b40a@fserv2000.net>
2001-10-17 12:38 ` Shirish Kalele
2001-10-17 17:58 ` kuznet [this message]
2001-10-17 18:38 ` Trond Myklebust
[not found] <005a01c1579d$adab2100$3291b40a@fserv2000.net>
2001-10-17 18:39 ` kuznet
[not found] <00b401c157a1$8edd3f20$3291b40a@fserv2000.net>
2001-10-17 19:27 ` kuznet
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=200110171758.VAA22159@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=kalele@veritas.COM \
--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®