From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: root@chaos.analogic.com
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Chuck Lever <cel@citi.umich.edu>, Dan Kegel <dank@kegel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] new timeout behavior for RPC requests on TCP sockets
Date: Thu, 14 Nov 2002 20:33:40 +0100 [thread overview]
Message-ID: <15827.64148.272459.600067@helicity.uio.no> (raw)
In-Reply-To: <Pine.LNX.3.95.1021114133025.13043B-100000@chaos.analogic.com>
>>>>> " " == Richard B Johnson <root@chaos.analogic.com> writes:
> Because all of the RPC stuff was, initially, user-mode
> code. For performance reasons or otherwise, it was moved into
> the kernel. Okay, so far? Now, when something goes wrong with
> that code, should that code be fixed, or should the unrelated
> TCP/IP code be modified to accommodate? I think the time-outs
> should be put at the correct places and not added to generic
> network code.
No. The kernel RPC code has never been user mode code, nor has it ever
been exported to userland. It exists purely for the benefit of NFS and
friends. It is located in a subdirectory of the network code, but it
is certainly not 'generic network code'.
Cheers,
Trond
next prev parent reply other threads:[~2002-11-14 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 23:48 Dan Kegel
2002-11-13 15:58 ` Chuck Lever
2002-11-13 16:44 ` Richard B. Johnson
2002-11-13 16:49 ` Trond Myklebust
2002-11-13 18:38 ` Richard B. Johnson
2002-11-14 15:41 ` Trond Myklebust
2002-11-14 18:36 ` Richard B. Johnson
2002-11-14 19:33 ` Trond Myklebust [this message]
2002-11-14 20:26 ` Chuck Lever
2002-11-14 20:37 ` Richard B. Johnson
2002-11-14 21:05 ` Chuck Lever
2002-11-13 17:42 ` Alan Cox
2002-11-13 18:33 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 19:57 Chuck Lever
2002-11-12 23:15 Chuck Lever
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=15827.64148.272459.600067@helicity.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=cel@citi.umich.edu \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®