Re: [PATCH 0/7] Remaining rpcbind patches for 2.6.27

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Jul 7, 2008, at 4:51 PM, Trond Myklebust wrote:

On Mon, 2008-07-07 at 15:44 -0400, Chuck Lever wrote:

If you would like connected UDP, I won't object to you implementing
it.  However, I never tested whether a connected UDP socket will give
the desired semantics without extra code in the UDP transport (for
example, an ->sk_error callback). I don't think it's worth the hassle if we have to add code to UDP that only this tiny use case would need.


OK. I'll set these patches aside until I have time to look into adding
connected UDP support.

That's not completely necessary... the one-shot + TCP changes just make it nicer when the local rpcbind is not listening. Without these, the cases where the rpcbind daemon isn't running, or doesn't support rpcbind v3/v4 and the kernel was built with CONFIG_SUNRPC_REGISTER_V4, will cause some delays before failing, but otherwise shouldn't be a problem.

I think you can drop the patch to change rpcb registration to go over TCP for now unless you already have a CUDP implementation you are happy with.

I know a lot of folks are waiting for IPv6 support to appear, and I don't want this detail to hang it up.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux