From: Jesse Gross <jesse@nicira.com>
To: Thomas Graf <tgraf@redhat.com>
Cc: "dev@openvswitch.org" <dev@openvswitch.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v3] linux: Report supported user features to the kernel
Date: Fri, 20 Dec 2013 10:20:21 -0800 [thread overview]
Message-ID: <CAEP_g=9Asc30igbvSAdzUTEHFSDrGPrUizeNw1pegM6d62OZhA@mail.gmail.com> (raw)
In-Reply-To: <399ecc79d2539f4624d9b5363f37c8d358571fae.1387466318.git.tgraf@redhat.com>
On Thu, Dec 19, 2013 at 7:20 AM, Thomas Graf <tgraf@redhat.com> wrote:
> Following commit (''netlink: Do not enforce alignment of last Netlink
> attribute''), signal the ability to receive unaligned Netlink messages
> to the datapath to enable utilization of zerocopy optimizations.
>
> Opening a datapath is now done by issueing a OVS_DP_CMD_SET in order
> to overwrite previously set user features.
>
> Signed-off-by: Thomas Graf <tgraf@redhat.com>
Applied, thanks.
prev parent reply other threads:[~2013-12-20 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 15:20 [PATCH v3] linux: Report supported user features to the kernel Thomas Graf
2013-12-19 18:14 ` [ovs-dev] " Ben Pfaff
2013-12-20 18:20 ` Jesse Gross [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='CAEP_g=9Asc30igbvSAdzUTEHFSDrGPrUizeNw1pegM6d62OZhA@mail.gmail.com' \
--to=jesse@nicira.com \
--cc=dev@openvswitch.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@redhat.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).