From: Chuck Lever <chuck.lever@oracle.com>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [RFC] [PATCH] rpcbind netid declared per-transport
Date: Fri, 31 Aug 2007 12:59:39 -0400 [thread overview]
Message-ID: <46D848FB.6070409@oracle.com> (raw)
In-Reply-To: <EXNANE01FlmmlQ080Gx00000245@exnane01.hq.netapp.com>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Talpey, Thomas wrote:
> At 12:27 PM 8/31/2007, Chuck Lever wrote:
>> Talpey, Thomas wrote:
>>> "RPCB_" prefix: They're (with this patch) part of the rpcbind api. The prefix
>> ...
>> It's a nit, I guess.
>
> How about RPCBIND_NETID_foo? It's more obvious, and keeps the RPC...
OK by me.
>>> RPCB_MAXNETIDLEN: Sure, I'll move it. It is, after all, a limit on the string
>>> ...
>> We need to know the maximum size to compute the largest possible size of
>> the RPC buffer needed for the request. See the definition of
>> RPCB_netid_sz. Those are all added together to get the largest possible
>> request size, and that's used to compute the largest possible buffer size.
>
> Yes, I know, but it could be larger and more dynamically calculated.
I'm not sure what you mean, then. The buffer size maximums are
statically computed at kernel compile time.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-31 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 13:35 [RFC] [PATCH] rpcbind netid declared per-transport Talpey, Thomas
2007-08-31 14:08 ` Chuck Lever
2007-08-31 14:26 ` Trond Myklebust
2007-08-31 14:30 ` Chuck Lever
2007-08-31 15:13 ` Trond Myklebust
2007-08-31 15:38 ` Chuck Lever
2007-08-31 16:08 ` Talpey, Thomas
2007-08-31 16:27 ` Chuck Lever
2007-08-31 16:41 ` Talpey, Thomas
2007-08-31 16:59 ` Chuck Lever [this message]
2007-08-31 14:33 ` Chuck Lever
2007-08-31 14:32 ` 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=46D848FB.6070409@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Thomas.Talpey@netapp.com \
--cc=nfs@lists.sourceforge.net \
/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.