From: Kirill Kolyshkin <kir@virtuozzo.com>
To: Andrey Vagin <avagin@virtuozzo.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Eric Dumazet <edumazet@google.com>,
David Ahern <dsahern@gmail.com>,
Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Netlink engine issues, and ways to fix those
Date: Thu, 3 Nov 2016 21:04:07 +0000 [thread overview]
Message-ID: <AM4PR0802MB2355F0B4ACE8B60CBED91709A9A30@AM4PR0802MB2355.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
Just to remind you, the session is about to begin, it's Coronado room.
On Nov 3, 2016 9:41 AM, Andrey Vagin <avagin@openvz.org> wrote:
Hi All,
The session is scheduled to Thursday at 3pm:
Title: Netlink engine issues, and ways to fix those
https://www.linuxplumbersconf.org/2016/ocw/proposals/4599
[-- Attachment #2: Type: text/html, Size: 844 bytes --]
next reply other threads:[~2016-11-03 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 21:04 Kirill Kolyshkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-03 5:20 Andrei Vagin
2016-09-04 19:03 ` Andy Lutomirski
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
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=AM4PR0802MB2355F0B4ACE8B60CBED91709A9A30@AM4PR0802MB2355.eurprd08.prod.outlook.com \
--to=kir@virtuozzo.com \
--cc=ast@plumgrid.com \
--cc=avagin@virtuozzo.com \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=kaber@trash.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pablo@netfilter.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