From: kuznet@ms2.inr.ac.ru
Message-Id: <200111191952.WAA21731@ms2.inr.ac.ru>
Subject: Re: more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 client
To: trond.myklebust@fys.uio.no
Date: Mon, 19 Nov 2001 22:52:28 +0300 (MSK)
Cc: b.lammering@science-computing.de, linux-kernel@vger.kernel.org
In-Reply-To: <15353.23941.858943.218040@charged.uio.no> from "Trond Myklebust" at Nov 19, 1 08:29:09 pm
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org

Hello!

> The problem is that when EAGAIN is returned by sendmsg,

BTW this is already problem. UDP should not hit EAGAIN case, if the
predicate is right.


> requests), and then reactivate it as soon as sock_wspace() reports
> that the available free buffer space is large enough to fit the next
> request.

sock_wspace() is OK. sock_writable() is bad.


> released and that sock_wspace() does indeed reflect more or less the
> maximum message size for which there is free buffer space (I allow a
> couple of kilobytes for extra padding)

Do not economize. :-) The longer you wait the less you scheduled.
We used to wait for half of sndbuf to be freed.


>						 then the current UDP code
> should be correct and race-free.

BTW recently I was reported it deadlocks on some spinlock...

Alexey
-
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/