All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: trond.myklybust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: [PATCH 06/14] SUNRPC: introduce rpcbind: replacement for in-kernel portmapper
Date: Fri, 19 Jan 2007 16:54:54 -0500	[thread overview]
Message-ID: <45B13E2E.4060609@oracle.com> (raw)
In-Reply-To: <20070119000952.GB13473@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

Christoph Hellwig wrote:
> On Thu, Jan 18, 2007 at 06:30:12PM -0500, Chuck Lever wrote:
>> Introduce a replacement for the in-kernel portmapper client that supports
>> all 3 versions of the rpcbind protocol.  This code is not used yet.
>>
>> Original code by Groupe Bull updated for the latest kernel, with multiple
>> bug fixes.
>>
>> Note that rpcb_clnt.c does not yet support registering via versions 3 and
>> 4 of the rpcbind protocol.
> 
> I don't quite like the way you introduce rcpbind.  It exports the same
> API as the old portmap service, just using the rpcb_ prefix instead
> of rpc_.  Why don't you transpar�ntly switch over the implementation to
> the new model?

Using a different name means both the old and new implementation can 
coexist in the kernel until we're sure the new one is working correctly. 
    This is a widely-used change management technique.

In addition, the new naming echoes the API naming scheme used in user space.

> More comments on the actual code:
> 
>> --- /dev/null
>> +++ b/net/sunrpc/rpcb_clnt.c
>> @@ -0,0 +1,539 @@
>> +/*
>> + * linux/net/sunrpc/rpcb_clnt.c
> 
> Please don't mention the filename in the top of file comment.  It's useless
> and even worse easily gets out of sync and confuses people then.

Done.

>> +static inline struct rpcbind_args *rpcb_map_alloc(void)
>> +{
>> +	return kzalloc(sizeof(struct rpcbind_args), GFP_ATOMIC);
>> +}
>> +
>> +static inline void rpcb_map_free(struct rpcbind_args *map)
>> +{
>> +	kfree(map);
>> +}
> 
> Please kill these useless wrappers.

I don't agree that these are useless.  This is a common defensive 
programming technique that is used throughout the Linux NFS and RPC 
implementation.  Placing these two functions next to each other 
documents in 9 lines of code which memory pool is used for rpcb_maps, 
and ensures that if the memory pool is changed, every instance of 
allocation and release is affected.  It also enforces the pointer types 
automatically.

>> +static struct rpc_clnt *rpcb_create(char *hostname, struct sockaddr *srvaddr, int proto, int version, int privileged)
> 
> Please make sure to properly break lines after 80 chars.

Done.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 276 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture Linux Projects Group
email;internet:chuck dot lever at nospam oracle dot com
title:Principle Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-01-19 21:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 23:23 [PATCH 00/14] NFS/RPC client patches for 2.6.21 Chuck Lever
2007-01-18 23:29 ` [PATCH 01/14] NFS: fix print format for tk_pid Chuck Lever
2007-01-19  0:03   ` Christoph Hellwig
2007-01-19  0:10     ` Chuck Lever
2007-01-18 23:29 ` [PATCH 02/14] SUNRPC: fix print format for tk_pid in auth_gss support Chuck Lever
2007-01-18 23:29 ` [PATCH 03/14] SUNRPC: fix print format for tk_pid Chuck Lever
2007-01-18 23:29 ` [PATCH 04/14] SUNRPC: Eliminate side effects from rpc_malloc Chuck Lever
2007-01-18 23:30 ` [PATCH 05/14] SUNRPC: Make rpc_free API more generic Chuck Lever
2007-01-18 23:30 ` [PATCH 06/14] SUNRPC: introduce rpcbind: replacement for in-kernel portmapper Chuck Lever
2007-01-19  0:09   ` Christoph Hellwig
2007-01-19 21:54     ` Chuck Lever [this message]
2007-01-18 23:30 ` [PATCH 07/14] SUNRPC: switch socket-based RPC transports to use rpcbind Chuck Lever
2007-01-18 23:30 ` [PATCH 08/14] SUNRPC: switch the RPC server to use the new rpcbind registration API Chuck Lever
2007-01-18 23:30 ` [PATCH 09/14] NFS: switch NFSROOT to use new rpcbind client Chuck Lever
2007-01-18 23:30 ` [PATCH 10/14] SUNRPC: Enable support for rpcbind versions 3 and 4 via CONFIG options Chuck Lever
2007-01-19  0:11   ` Christoph Hellwig
2007-01-19 22:04     ` Chuck Lever
2007-01-19 22:10       ` Trond Myklebust
2007-01-18 23:30 ` [PATCH 11/14] SUNRPC: remove old portmapper Chuck Lever
2007-01-18 23:30 ` [PATCH 12/14] SUNRPC: RPC buffer size estimates are too large Chuck Lever
2007-01-18 23:49   ` J. Bruce Fields
2007-01-18 23:54     ` Chuck Lever
2007-01-19  0:00       ` J. Bruce Fields
2007-01-19  0:08         ` Chuck Lever
2007-01-19 22:36   ` Trond Myklebust
2007-01-19 22:46     ` Chuck Lever
2007-01-19 23:12       ` Trond Myklebust
2007-01-23 16:04         ` Chuck Lever
2007-01-18 23:30 ` [PATCH 13/14] NLM: Shrink the maximum request size of NLM4 requests Chuck Lever
2007-01-19  0:13   ` Christoph Hellwig
2007-01-19 22:27     ` Chuck Lever
2007-01-20  9:26       ` Christoph Hellwig
2007-01-18 23:31 ` [PATCH 14/14] SUNRPC: Debugging aid Chuck Lever
2007-01-19 22:28   ` Trond Myklebust
2007-01-19 22:38     ` 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=45B13E2E.4060609@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=hch@infradead.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklybust@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 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.