From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 0/7] [RFC] kernel: add a netlink interface to get information about processes Date: Tue, 17 Feb 2015 09:53:09 +0100 Message-ID: <3238376.TxgiSSEfbZ@wuerfel> References: <1424161226-15176-1-git-send-email-avagin@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <1424161226-15176-1-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andrey Vagin Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Oleg Nesterov , Andrew Morton , Cyrill Gorcunov , Pavel Emelyanov , Roger Luethi List-Id: linux-api@vger.kernel.org On Tuesday 17 February 2015 11:20:19 Andrey Vagin wrote: > task_diag is based on netlink sockets and looks like socket-diag, which > is used to get information about sockets. > > A request is described by the task_diag_pid structure: > > struct task_diag_pid { > __u64 show_flags; /* specify which information are required */ > __u64 dump_stratagy; /* specify a group of processes */ > > __u32 pid; > }; Can you explain how the interface relates to the 'taskstats' genetlink API? Did you consider extending that interface to provide the information you need instead of basing on the socket-diag? Arnd