From: kuznet@ms2.inr.ac.ru
To: trond.myklebust@fys.uio.no
Cc: b.lammering@science-computing.de, linux-kernel@vger.kernel.org
Subject: Re: more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 client
Date: Mon, 19 Nov 2001 22:09:00 +0300 (MSK) [thread overview]
Message-ID: <200111191909.WAA21357@ms2.inr.ac.ru> (raw)
In-Reply-To: <15353.21949.239139.993379@charged.uio.no> from "Trond Myklebust" at Nov 19, 1 07:55:57 pm
Hello!
> Originally I had a test for whether sock_wspace(sk) was greater than
> some minimal value. We need this for UDP in order to avoid waking up
> 'rpciod' before the socket buffer is large enough to accommodate the
> RPC datagram.
I do no think this was right, to be honest. write_space with udp is
too hairy thing to use it correctly. :-) Anyway, it is enough to select
right sndbuf. Right is... well, default value is right. :-)
> As the same code worked in 2.2.x for TCP, I had assumed
> it was OK...
Most likely, it worked because 2.2 did not protect of overschedule
and waked up thread each time when some space was freed, so it was enough
that wakeup predicate used by tcp and by application had one common point:
wmem_alloc==0 and they always have it. 2.4 does not wake
up process, if it did not see full buffer after previous wakeup.
Alexey
next prev parent reply other threads:[~2001-11-19 19:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15349.39320.876188.274548@charged.uio.no>
2001-11-15 21:29 ` nfs problem: hp-server --- linux 2.4.13 client, ooops Birger Lammering
2001-11-15 23:58 ` Trond Myklebust
2001-11-16 11:45 ` nfs problem: hp|aix-server --- linux 2.4.15pre5 client Trond Myklebust
2001-11-16 12:01 ` Miquel van Smoorenburg
2001-11-16 12:24 ` Trond Myklebust
2001-11-16 11:24 ` Birger Lammering
2001-11-16 13:19 ` nfs problem: aix-server " Birger Lammering
2001-11-19 10:20 ` IPV4 socket layer, was: " Birger Lammering
2001-11-19 11:16 ` Alan Cox
2001-11-19 18:22 ` more tcpdumpinfo for nfs3 " Trond Myklebust
2001-11-19 18:49 ` kuznet
2001-11-19 18:55 ` Trond Myklebust
2001-11-19 19:09 ` kuznet [this message]
2001-11-19 19:29 ` Trond Myklebust
2001-11-19 19:52 ` kuznet
2001-11-19 20:38 ` Trond Myklebust
2001-11-19 21:17 ` Trond Myklebust
2001-11-20 17:42 ` kuznet
2001-11-20 19:39 ` Trond Myklebust
2001-11-20 19:45 ` kuznet
2001-11-20 20:29 ` Trond Myklebust
2001-11-21 10:07 ` Trond Myklebust
2001-11-21 17:05 ` kuznet
2001-11-20 20:05 ` Trond Myklebust
2001-11-20 20:18 ` David S. Miller
2001-11-20 20:28 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux kuznet
2001-11-20 17:41 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 client kuznet
2001-11-19 16:37 ` Birger Lammering
2001-11-20 9:26 ` Birger Lammering
2001-11-21 19:09 Manfred Spraul
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=200111191909.WAA21357@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=b.lammering@science-computing.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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®