From: Andy Lutomirski <luto@amacapital.net>
To: Andrei Vagin <avagin@virtuozzo.com>
Cc: Kirill Kolyshkin <kir@openvz.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
David Ahern <dsahern@gmail.com>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Netlink engine issues, and ways to fix those
Date: Sun, 4 Sep 2016 12:03:18 -0700 [thread overview]
Message-ID: <CALCETrV+=uJ1bqfHN+LkFZXho-8GjbEd6joBELCwvnk=rg0Skw@mail.gmail.com> (raw)
In-Reply-To: <20160903052014.GA4850@outlook.office365.com>
On Fri, Sep 2, 2016 at 10:20 PM, Andrei Vagin <avagin@virtuozzo.com> wrote:
> The netlink interface proved itself as a great way to perform
> descriptor-based kernel/userspace communication. It is especially useful
> for cases involving a big amount of data to transfer. The netlink
> communication protocol is simple and elegant; it also allows to extend
> the message format without breaking backward compatibility.
I'm interested, surprise surprise :)
next prev parent reply other threads:[~2016-09-04 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 5:20 Andrei Vagin
2016-09-04 19:03 ` Andy Lutomirski [this message]
2016-09-05 19:30 ` Alexei Starovoitov
2016-09-06 16:05 ` Stephen Hemminger
2016-09-12 14:05 ` Hannes Reinecke
2016-09-13 17:29 ` Eric W. Biederman
2016-09-16 5:58 ` Andrei Vagin
2016-09-18 20:18 ` Eric W. Biederman
2016-10-11 2:13 ` Andrei Vagin
2016-10-11 14:14 ` Alexey Dobriyan
2016-11-01 3:15 ` Andrei Vagin
2016-11-01 14:58 ` James Bottomley
2016-11-01 16:39 ` Theodore Ts'o
[not found] ` <CANaxB-ycZFtZW3=WasEDXgBwf3NF4C46aNwTOpKqHjuPbN5e-Q@mail.gmail.com>
2016-11-03 15:41 ` Andrey Vagin
2016-11-03 21:04 Kirill Kolyshkin
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='CALCETrV+=uJ1bqfHN+LkFZXho-8GjbEd6joBELCwvnk=rg0Skw@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=avagin@virtuozzo.com \
--cc=dsahern@gmail.com \
--cc=kaber@trash.net \
--cc=kir@openvz.org \
--cc=ksummit-discuss@lists.linuxfoundation.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