|
On Tue, Sep 21, 2010 at 12:46:53PM -0500, Seth Call wrote:
> Simon,
>
> Thanks for the quick response.
>
> So, we are new to LVS and completely not kernel developers. Fine...
>
> So our thoughts are to first use sh as-is, because it'll work for testing,
> development, and to some degree production.
>
> So once we know we are using LVS as the project goes further, we can build
> 'sh2'.
>
> I was going to find the sh code and at least get an idea of how difficult
> it'd be to make a sh2. It sounds trivial to me, given that sh already
> exists--but it would be a new environment so that'd be the main issue.
I agree with that analysis.
For reference, the sh code is in net/netfilter/ipvs/ip_vs_sh.c
in the kernel tree. Development usually occurs against
Patrick McHardy's nf-next-2.6 tree which is on git.kernel.org.
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
