From: David Miller <davem@davemloft.net>
To: amirv@mellanox.com
Cc: netdev@vger.kernel.org, ogerlitz@mellanox.com,
hadarh@mellanox.com, yanb@mellanox.com
Subject: Re: [PATCH V1 net-next 0/4] Add destination MAC address to ethtool flow steering
Date: Wed, 12 Dec 2012 13:03:08 -0500 (EST) [thread overview]
Message-ID: <20121212.130308.47366656526056501.davem@davemloft.net> (raw)
In-Reply-To: <1355314400-14909-1-git-send-email-amirv@mellanox.com>
From: Amir Vadai <amirv@mellanox.com>
Date: Wed, 12 Dec 2012 14:13:16 +0200
> From: Yan Burman <yanb@mellanox.com>
>
> In vSwitch configuration it is often beneficial to create flow steering
> rules for L3/L4 traffic based on VM port. This requires destination MAC
> address of that port to be present. Note that today the mlx4_en driver
> adds the mac address of itself to the flow spec, where under the new
> ethtool flag suggested here it doesn't.
>
> It may also be useful in macvlan devices.
>
> These patches add kernel support for the new field (does not break old
> userspace compatibility, so new ethtool will work on old kernels and
> old ethtool will work with new kernels).
>
> Also present here is the ethtool userspace patch.
>
> See more details here http ://marc.info/?t=134977576500003
Kernel side applied to net-next, thanks.
prev parent reply other threads:[~2012-12-12 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 12:13 [PATCH V1 net-next 0/4] Add destination MAC address to ethtool flow steering Amir Vadai
2012-12-12 12:13 ` [PATCH V1 net-next 1/3] net: ethtool: Add destination MAC address to flow steering API Amir Vadai
2012-12-12 18:28 ` Ben Hutchings
2012-12-12 20:40 ` Amir Vadai
2012-12-12 12:13 ` [PATCH V1 net-next 2/3] net/mlx4_en: Use generic etherdevice.h functions Amir Vadai
2012-12-12 12:13 ` [PATCH V1 net-next 3/3] net/mlx4_en: Add support for destination MAC in steering rules Amir Vadai
2012-12-12 12:13 ` [PATCH ETHTOOL] Added dst-mac parameter for L3/L4 flow spec rules. This is usefull in vSwitch configurations Amir Vadai
2012-12-12 18:03 ` 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=20121212.130308.47366656526056501.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=hadarh@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yanb@mellanox.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;
as well as URLs for NNTP newsgroup(s).