From: Ben Greear <greearb@candelatech.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 00/11] NFS: Support binding to source address
Date: Thu, 23 Jun 2011 09:05:48 -0700 [thread overview]
Message-ID: <4E03645C.5080503@candelatech.com> (raw)
In-Reply-To: <C4E3B7E9-47D7-4A93-B88F-0021D0450ACC@oracle.com>
On 06/23/2011 08:46 AM, Chuck Lever wrote:
> Hi Ben-
>
> On Jun 23, 2011, at 9:29 AM, Ben Greear wrote:
>
>> On 06/23/2011 07:59 AM, Chuck Lever wrote:
>>>
>>> On Jun 22, 2011, at 3:36 PM, greearb@candelatech.com wrote:
>>>
>>>> From: Ben Greear<greearb@candelatech.com>
>>>>
>>>> This lets one specify the source IP address for
>>>> sockets, allowing users to leverage routing rules
>>>> on multi-homed systems.
>>>
>>> Do you need changes to send NLM requests from the right source address?
>>
>> Not for my testing so far...but maybe I'm not utilizing whatever NLM
>> does. What sort of things would require/use it?
>
> File locking. NLM support should be a requirement for a complete implementation of srcaddr=, IMO.
Ok, I think I have some patches for this already, but didn't re-add them when
breaking up the big patch for submission. I'll set up a test case with
file locking and double-check that I have it working correctly.
Thanks,
Ben
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-06-23 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 21:36 [PATCH 00/11] NFS: Support binding to source address greearb
2011-06-22 21:36 ` [PATCH 01/11] sunrpc: Don't attempt to bind to AF_UNSPEC address greearb
2011-06-22 21:36 ` [PATCH 02/11] nfs: Two AF_UNSPEC addresses should always match each other greearb
2011-06-22 21:36 ` [PATCH 03/11] nfs: Add srcaddr member to nfs_client greearb
2011-06-22 21:36 ` [PATCH 04/11] nfs: Use request destination addr as callback source addr greearb
2011-06-22 21:36 ` [PATCH 05/11] nfs: Pay attention to srcaddr in v4.1 callback logic greearb
2011-06-22 21:36 ` [PATCH 06/11] nfs: Use srcaddr in nfs_match_client greearb
2011-06-22 21:36 ` [PATCH 07/11] nfs: Add srcaddr to /proc/fs/nfsfs/servers greearb
2011-06-22 21:36 ` [PATCH 08/11] nfs: Pass srcaddr into mount request greearb
2011-06-22 21:36 ` [PATCH 09/11] nfs: Propagate src-addr in client code greearb
2011-06-22 21:36 ` [PATCH 10/11] nfs: Bind to srcaddr in rpcb_create greearb
2011-06-22 21:36 ` [PATCH 11/11] nfs: Support srcaddr= to bind to specific IP address greearb
2011-06-23 14:59 ` [PATCH 00/11] NFS: Support binding to source address Chuck Lever
2011-06-23 15:29 ` Ben Greear
2011-06-23 15:46 ` Chuck Lever
2011-06-23 16:05 ` Ben Greear [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=4E03645C.5080503@candelatech.com \
--to=greearb@candelatech.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).