netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Julius Volz" <juliusv@google.com>
To: "Joseph Mack NA3T" <jmack@wm7d.net>
Cc: netdev@vger.kernel.org, lvs-devel@vger.kernel.org
Subject: Re: [PATCH] Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs in preparation for IPv6 support
Date: Wed, 7 May 2008 17:51:54 +0200	[thread overview]
Message-ID: <f4845fc0805070851y7f1f00d0xd2dfcc7feb79c173@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805070734580.6164@wm7d.net>

Hi Joe,

On Wed, May 7, 2008, Joseph Mack NA3T wrote:
>  With the little time lvs developers have had for ipv6 so far, you're not
> likely to get much feedback from people here I'm sorry to say.

Hm, ok. This patch doesn't touch any functionality though. It only
moves files from one directory to another, so it's merely cosmetics,
no IPv6 knowledge required. Of course, we could still do the move
later, after some IPv6 code is actually in IPVS. If there is no
reaction, I'll just continue working under net/ipv4/ipvs for now. No
big deal.

>  The people who are interested in ipv6 have posted to the mailing list. Some
> of them may still be interested in lvs-ipv6 and in testing patches. Looking
> for ipv6 in
>
>  http://marc.info/?l=linux-virtual-server&m=116664927421172&w=2
>
>  [addresses]

Thank you! Good to have interested people for testing later on. We
also have some, but different people and organizations have different
setups and edge cases to help testing.

The other code I have at the moment compiles (sometimes), but doesn't
do much more. It needs much more work to actually do something again
with either IP version.

>  Seiji Tsuchiike <tsuchiike () yggr-drasill ! com> #the original ipv6
> implementation for LVS, doesn't respond to e-mail and is not findable with
> google.

Yes, he and his code seem to have disappeared...

>  "Fernanda G Weiden" <fernanda@softwarelivre.org> #I think she's with you

Yes! :)

>  A pair of people working for a company installing gear at govt sites was
> interested enough in getting an ipv6 port of LVS to offer Horms some money
> for his time, but Horms didn't have time at any price. You'd think I'd be
> able to find the e-mail from these people, but apparently I can't think of
> the correct grep string.

Ok, thanks. Let me know in case you stumble over it!

>  You might e-mail all these people above and as well put out notices of new
> releases of code onto the regular LVS mailing list. Someone may be
> listening, or they'll pick it up from one of the archivers.

Yes, once there is code that does something useful! At the moment, it
seems like a hamburger too big to get a good first bite at. But I'm
working on it...

Thanks for responding once again, Joe!

Julius

-- 
Google Switzerland GmbH

  reply	other threads:[~2008-05-07 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 14:32 [PATCH] Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs in preparation for IPv6 support Julius Volz
2008-05-07 15:00 ` Joseph Mack NA3T
2008-05-07 15:51   ` Julius Volz [this message]
2008-05-09 12:49     ` Joseph Mack NA3T
2008-05-09 13:21       ` Jason Stubbs
2008-05-09 13:47         ` Julius Volz
2008-05-09 13:46       ` Julius Volz
  -- strict thread matches above, loose matches on Subject: below --
2008-04-04 10:40 Julius Volz
2008-04-05  1:07 ` Simon Horman
2008-04-05 10:17   ` Julius Volz

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=f4845fc0805070851y7f1f00d0xd2dfcc7feb79c173@mail.gmail.com \
    --to=juliusv@google.com \
    --cc=jmack@wm7d.net \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@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).