From: Ben Greear <greearb@candelatech.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: PATCH: Support binding to a local IPv4 address when mounting a server.
Date: Sun, 22 Feb 2009 15:45:16 -0800 [thread overview]
Message-ID: <49A1E38C.2050607@candelatech.com> (raw)
In-Reply-To: <1235346094.7331.111.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
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
next prev parent reply other threads:[~2009-02-22 23:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 1:01 PATCH: Support binding to a local IPv4 address when mounting a server Ben Greear
2009-01-22 2:38 ` Chuck Lever
2009-01-22 5:35 ` Ben Greear
2009-01-22 17:06 ` Chuck Lever
2009-01-22 17:31 ` Ben Greear
2009-01-23 17:18 ` Chuck Lever
2009-01-23 17:39 ` Ben Greear
2009-02-21 7:43 ` Ben Greear
2009-02-21 17:16 ` Trond Myklebust
2009-02-21 22:09 ` Chuck Lever
2009-02-22 5:52 ` Ben Greear
2009-02-22 19:09 ` Trond Myklebust
[not found] ` <1235329791.7331.75.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-22 20:29 ` Chuck Lever
2009-02-22 22:01 ` Trond Myklebust
2009-02-22 23:17 ` Ben Greear
2009-02-22 23:41 ` Trond Myklebust
[not found] ` <1235346094.7331.111.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-22 23:45 ` Ben Greear [this message]
2009-02-22 6:24 ` Ben Greear
2009-02-22 20:01 ` Chuck Lever
2009-02-22 7:05 ` Ben Greear
-- strict thread matches above, loose matches on Subject: below --
2009-02-21 18:18 Ben Greear
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=49A1E38C.2050607@candelatech.com \
--to=greearb@candelatech.com \
--cc=chuck.lever@oracle.com \
--cc=kaber@trash.net \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox