All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Gartrell <agartrell@fb.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: horms@verge.net.au, lvs-devel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH ipvs,v4 19/20] ipvs: use the new dest addr family field
Date: Fri, 29 Aug 2014 14:19:04 -0700	[thread overview]
Message-ID: <5400EE48.5060007@fb.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1408291259510.4876@ja.home.ssi.bg>

Hey

On 8/29/14 3:32 AM, Julian Anastasov wrote:
>
> 	Hello,
>
> On Fri, 29 Aug 2014, Alex Gartrell wrote:
>
>> From: Julian Anastasov <ja@ssi.bg>
>>
>> Use the new address family field cp->daf when printing
>> cp->daddr in logs or connection listing.
>>
>> Signed-off-by: Julian Anastasov <ja@ssi.bg>
>> Signed-off-by: Alex Gartrell <agartrell@fb.com>
>
> ...
>
>> --- a/net/netfilter/ipvs/ip_vs_conn.c
>> +++ b/net/netfilter/ipvs/ip_vs_conn.c
>> @@ -27,6 +27,7 @@
>>
>>   #include <linux/interrupt.h>
>>   #include <linux/in.h>
>> +#include <linux/inet.h>
>>   #include <linux/net.h>
>>   #include <linux/kernel.h>
>>   #include <linux/module.h>
>> @@ -77,6 +78,13 @@ static unsigned int ip_vs_conn_rnd __read_mostly;
>>   #define CT_LOCKARRAY_SIZE  (1<<CT_LOCKARRAY_BITS)
>>   #define CT_LOCKARRAY_MASK  (CT_LOCKARRAY_SIZE-1)
>>
>> +/* We need an addrstrlen that works with or without v6 */
>> +#ifdef CONFIG_IP_VS_IPV6
>> +#define IP_VS_ADDRSTRLEN INET6_ADDRSTRLEN
>> +#else
>> +#define IP_VS_ADDRSTRLEN INET_ADDRSTRLEN
>> +#endif
>
> 	Thanks! Note that for v4 we use 8+1 (hex).
> All other patches look ok. It is early to ack them,
> right? We need to post them again at the right time.
> I hope "ipvs: properly declare tunnel encapsulation"
> will be moved further soon.

I updated this patch

-#define IP_VS_ADDRSTRLEN INET_ADDRSTRLEN
+#define IP_VS_ADDRSTRLEN (8+1)

I'll spare the mailing list another 20 emails though.

So, if I understand correctly, we'll wait until it lands in net-next and 
then I'll submit these patches to netdev?


>
> 	For now we have to find a way to support sync
> protocol and to update ipvsadm.

I'll mail the ipvsadm change right away.  I haven't begun to think about 
sync protocol though :)

Thanks,
Alex

  reply	other threads:[~2014-08-29 21:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  8:38 [PATCH ipvs,v4 00/20] Support v6 real servers in v4 pools and vice versa Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 01/20] ipvs: Add destination address family to netlink interface Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 02/20] ipvs: Supply destination addr family to ip_vs_{lookup_dest,find_dest} Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 03/20] ipvs: Pass destination address family to ip_vs_trash_get_dest Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 04/20] ipvs: Supply destination address family to ip_vs_conn_new Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 05/20] ipvs: prevent mixing heterogeneous pools and synchronization Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 06/20] ipvs: Pull out crosses_local_route_boundary logic Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 07/20] ipvs: Pull out update_pmtu code Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 08/20] ipvs: Add generic ensure_mtu_is_adequate to handle mixed pools Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 09/20] ipvs: support ipv4 in ipv6 and ipv6 in ipv4 tunnel forwarding Alex Gartrell
2014-08-29  8:38 ` [PATCH ipvs,v4 10/20] ipvs: address family of LBLC entry depends on svc family Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 11/20] ipvs: address family of LBLCR " Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 12/20] ipvs: use correct address family in DH logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 13/20] ipvs: use correct address family in LC logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 14/20] ipvs: use correct address family in NQ logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 15/20] ipvs: use correct address family in RR logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 16/20] ipvs: use correct address family in SED logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 17/20] ipvs: use correct address family in SH logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 18/20] ipvs: use correct address family in WLC logs Alex Gartrell
2014-08-29  8:39 ` [PATCH ipvs,v4 19/20] ipvs: use the new dest addr family field Alex Gartrell
2014-08-29 10:32   ` Julian Anastasov
2014-08-29 21:19     ` Alex Gartrell [this message]
2014-08-30  8:35       ` Julian Anastasov
2014-09-01  1:17         ` Simon Horman
2014-09-09 19:41       ` Julian Anastasov
2014-09-09 23:22         ` Alex Gartrell
2014-09-10  6:05           ` Julian Anastasov
2014-08-29  8:39 ` [PATCH ipvs,v4 20/20] ipvs: Allow heterogeneous pools now that we support them Alex Gartrell

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=5400EE48.5060007@fb.com \
    --to=agartrell@fb.com \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=kernel-team@fb.com \
    --cc=lvs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.