From: David Miller <davem@davemloft.net>
To: felix.manlunas@cavium.com
Cc: netdev@vger.kernel.org, veerasenareddy.burru@cavium.com,
raghu.vatsavayi@cavium.com, derek.chickles@cavium.com,
satananda.burla@cavium.com
Subject: Re: [PATCH net-next] liquidio: add support for OVS offload
Date: Sat, 27 May 2017 20:06:56 -0400 (EDT) [thread overview]
Message-ID: <20170527.200656.1963846123525565873.davem@davemloft.net> (raw)
In-Reply-To: <20170527155633.GA2358@felix-thinkpad.cavium.com>
From: Felix Manlunas <felix.manlunas@cavium.com>
Date: Sat, 27 May 2017 08:56:33 -0700
> From: VSR Burru <veerasenareddy.burru@cavium.com>
>
> Add support for OVS offload. By default PF driver runs in basic NIC mode
> as usual. To run in OVS mode, use the insmod parameter "fw_type=ovs".
>
> For OVS mode, create a management interface for communication with NIC
> firmware. This communication channel uses PF0's I/O rings.
>
> Bump up driver version to 1.6.0 to match newer firmware.
>
> Signed-off-by: VSR Burru <veerasenareddy.burru@cavium.com>
> Signed-off-by: Felix Manlunas <felix.manlunas@cavium.com>
How does this work?
What in userspace installs the OVS rules onto the card?
We do not support direct offload of OVS, as an OVS entity, instead we
required all vendors to make their OVS offloads visible as packet
scheduler classifiers and actions.
The same rules apply to liquidio.
If there is some special set of userspace interfaces that are used to
comunicate with these different firmwares in some liquidio specific
way, I am going to be very upset. That is definitely not allowed.
I'm not applying this patch until the above is resolved and at least
more information is added to this commit log message to explain how
this stuff works.
next prev parent reply other threads:[~2017-05-28 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 15:56 [PATCH net-next] liquidio: add support for OVS offload Felix Manlunas
2017-05-28 0:06 ` David Miller [this message]
2017-06-04 20:43 ` Chickles, Derek
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=20170527.200656.1963846123525565873.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=derek.chickles@cavium.com \
--cc=felix.manlunas@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=raghu.vatsavayi@cavium.com \
--cc=satananda.burla@cavium.com \
--cc=veerasenareddy.burru@cavium.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).