From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dave Airlie <airlied@linux.ie>
Cc: NFS@lists.sourceforge.net
Subject: Re: TCP write queue full message..
Date: 28 Jan 2003 13:52:28 +0100 [thread overview]
Message-ID: <shsof61xwqb.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0301280600080.2079-100000@skynet>
>>>>> " " == Dave Airlie <airlied@linux.ie> writes:
> Now I'm running over UDP so I cannot understand where the TCP
> write queue full is coming from, (is the message just
> in-correct or should I never see it with UDP?? ).. the packet
> goes out on the wire over UDP and ethereal sees the corrupt RPC
> request...
Yeah, that's a bit of a historical misnomer: it is no longer a
TCP-specific write queue.
The above message just means that the socket is congested due to too
many outstanding requests, and that your request is therefore being
delayed until the congestion clears up.
Cheers,
Trond
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-01-28 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 6:09 TCP write queue full message Dave Airlie
2003-01-28 12:52 ` Trond Myklebust [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=shsof61xwqb.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=NFS@lists.sourceforge.net \
--cc=airlied@linux.ie \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.