From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754654AbcEDUWf (ORCPT <rfc822;w@1wt.eu>);
	Wed, 4 May 2016 16:22:35 -0400
Received: from mail-pf0-f178.google.com ([209.85.192.178]:33383 "EHLO
	mail-pf0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754297AbcEDUWd (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 4 May 2016 16:22:33 -0400
Date: Wed, 4 May 2016 13:22:45 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrey Vagin <avagin@openvz.org>
Cc: linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: task_diag: add a new interface to get information about
 processes
Message-ID: <20160504132245.1d04c131@xeon-e3>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

I understand how reading /proc or /sys can be a bottleneck, but this
proposed method using a system call is the wrong way to do this.

Why not use netlink like other systems do which allows a message
based response which allows for future changes (no fixed datastructures),
and is message based.

Generic netlink has already been used by several other subsystems.