From: Stephen Hemminger <stephen@networkplumber.org>
To: Serhey Popovych <serhe.popovych@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/6] utils: Get rid of inet_get_addr()
Date: Thu, 18 Jan 2018 10:35:02 -0800 [thread overview]
Message-ID: <20180118103502.59f0b196@xeon-e3> (raw)
In-Reply-To: <1516299227-26724-1-git-send-email-serhe.popovych@gmail.com>
On Thu, 18 Jan 2018 20:13:41 +0200
Serhey Popovych <serhe.popovych@gmail.com> wrote:
> It looks confusing to have multiple independent
> routines to get internet address from it's string
> representation: get_addr() and inet_get_addr().
>
> Most complicated users of inet_get_addr() is
> iplink_geneve.c and iplink_vxlan.c because they
> required to handle both AF_INET and AF_INET6
> for their local/remote endpoints.
>
> On the other hand get_addr() does not provide
> additional information like address type: need
> to address this. to get rid of current and
> possible future code duplications. Note that
> this functionality is first step to make proto
> independent handling of local/remote endpoints
> in ip/tunnel code (there will be additional
> series based on this one).
>
> Also fix get_addr_1() and get_prefix() to make
> sure it always provide correct ->family and
> ->bitlen.
>
> As always comments, suggestions and criticism
> are welcome.
>
> Thanks,
> Serhii
>
> Serhey Popovych (6):
> utils: Always specify family for address in get_addr_1()
> utils: Always specify family and ->bytelen in get_prefix_1()
> utils: Fast inet address classification after get_addr()
> iplink_geneve: Get rid of inet_get_addr()
> iplink_vxlan: Get rid of inet_get_addr()
> ip: Get rid of inet_get_addr()
>
> include/utils.h | 36 ++++++++++++++++-
> ip/iplink_geneve.c | 23 +++++------
> ip/iplink_vxlan.c | 72 ++++++++++++---------------------
> ip/iproute_lwtunnel.c | 5 ++-
> ip/ipseg6.c | 8 ++--
> lib/utils.c | 108 +++++++++++++++++++++++++++++--------------------
> 6 files changed, 142 insertions(+), 110 deletions(-)
>
Let's consider this for net-next.
Not for current release.
next prev parent reply other threads:[~2018-01-18 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 18:13 [PATCH iproute2 0/6] utils: Get rid of inet_get_addr() Serhey Popovych
2018-01-18 18:13 ` [PATCH iproute2 1/6] utils: Always specify family for address in get_addr_1() Serhey Popovych
2018-01-18 18:13 ` [PATCH iproute2 2/6] utils: Always specify family and ->bytelen in get_prefix_1() Serhey Popovych
2018-01-18 18:13 ` [PATCH iproute2 3/6] utils: Fast inet address classification after get_addr() Serhey Popovych
2018-01-18 18:13 ` [PATCH iproute2 4/6] iplink_geneve: Get rid of inet_get_addr() Serhey Popovych
2018-01-18 18:13 ` [PATCH iproute2 5/6] iplink_vxlan: " Serhey Popovych
2018-01-18 18:13 ` [PATCH iproute2 6/6] ip: " Serhey Popovych
2018-01-18 18:35 ` Stephen Hemminger [this message]
2018-01-21 18:13 ` [PATCH iproute2 0/6] utils: " David Ahern
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=20180118103502.59f0b196@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@gmail.com \
/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