From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v3] net: Require exact match for TCP socket lookups if dif is l3mdev
Date: Sat, 15 Oct 2016 19:32:36 -0400 (EDT) [thread overview]
Message-ID: <20161015.193236.1802271946749974666.davem@davemloft.net> (raw)
In-Reply-To: <48ba7600-0624-9684-e609-b7a315e03483@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Sat, 15 Oct 2016 17:07:53 -0600
> I believe at netconf someone mentioned it would be a great day when
> something is done for IPv6 first and IPv4 was a follow on. Here you
> go. :-)
:-)
> I can rename the existing one to skb_l3mdev_slave_6 and make the new
> one skb_l3mdev_slave_4.
That works. So does names with "ipv4_" and "ipv6_" prefixes which at
least to me seems more canonical. But maybe I'm just weird like that.
prev parent reply other threads:[~2016-10-15 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 19:29 [PATCH v3] net: Require exact match for TCP socket lookups if dif is l3mdev David Ahern
2016-10-15 21:46 ` David Miller
2016-10-15 23:07 ` David Ahern
2016-10-15 23:32 ` David Miller [this message]
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=20161015.193236.1802271946749974666.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=eric.dumazet@gmail.com \
--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).