[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-nfs
Subject:    Re: PATCH:  Support binding to a local IPv4 address when mounting
From:       Ben Greear <greearb () candelatech ! com>
Date:       2009-02-22 23:45:16
Message-ID: 49A1E38C.2050607 () candelatech ! com
[Download RAW message or body]

Trond Myklebust wrote:
> On Sun, 2009-02-22 at 15:17 -0800, Ben Greear wrote:
>   
>> My specific application is a testing tool that emulates 1000+ unique NFS 
>> clients,
>> primarily for testing  & loading NFS servers.
>> I put each client on a mac-vlan and put them all on the same subnet so 
>> that I don't
>> need any routers between my box and the nfs server.  (We can also put
>> them on different subnets and use different routers, and the specific 
>> source-ip
>> also helps there...)
>>
>> I use routing tricks to enforce that a particular source-IP uses a 
>> specific routing
>> table, and that ties pkts to a specific mac-vlan interface.  The mount 
>> bindaddr
>> option then binds a mount to a specific local IP and thus to a specific 
>> mac-vlan.
>>
>> This shows 1000+ mounts on my test box, and the nfs server sees 1000
>> unique clients (all with different MACs, IPS, etc).
>>     
>
> Any reason why you couldn't multi-home the server too, and use the
> destination IP address to control the route on the clients?
>   
I'm trying to emulate 1000 NFS clients running against a 'normal' NFS 
server,
and in that case, the NFS server would have a single (or small number of IP
addrs), and each client would have a unique IP and MAC.

Thanks,
Ben

>   Trond
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com


--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]