From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id BECFA722 for ; Sun, 4 Sep 2016 19:03:40 +0000 (UTC) Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 310C8176 for ; Sun, 4 Sep 2016 19:03:40 +0000 (UTC) Received: by mail-vk0-f46.google.com with SMTP id f76so62826890vke.0 for ; Sun, 04 Sep 2016 12:03:40 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160903052014.GA4850@outlook.office365.com> References: <20160903052014.GA4850@outlook.office365.com> From: Andy Lutomirski Date: Sun, 4 Sep 2016 12:03:18 -0700 Message-ID: To: Andrei Vagin Content-Type: text/plain; charset=UTF-8 Cc: Kirill Kolyshkin , "ksummit-discuss@lists.linuxfoundation.org" , David Ahern , Patrick McHardy Subject: Re: [Ksummit-discuss] [TECH TOPIC] Netlink engine issues, and ways to fix those List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Sep 2, 2016 at 10:20 PM, Andrei Vagin 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 :)