From: Balbir Singh <bsingharora@gmail.com>
To: Weiping Zhang <zwp10758@gmail.com>
Cc: sblbir@amazon.com, davem@davemloft.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2] taskstats: add /proc/taskstats to fetch pid/tgid status
Date: Wed, 27 Jan 2021 22:13:46 +1100 [thread overview]
Message-ID: <20210127111346.GB59838@balbir-desktop> (raw)
In-Reply-To: <CAA70yB5evFpMSy-D9txv91NNHTguXsSVstAFQ3sYTTkDMy6F=A@mail.gmail.com>
On Fri, Jan 22, 2021 at 10:07:50PM +0800, Weiping Zhang wrote:
> Hello Balbir Singh,
>
> Could you help review this patch, thanks
>
> On Mon, Dec 28, 2020 at 10:10 PM Weiping Zhang <zwp10758@gmail.com> wrote:
> >
> > Hi David,
> >
> > Could you help review this patch ?
> >
> > thanks
> >
> > On Fri, Dec 18, 2020 at 1:24 AM Weiping Zhang
> > <zhangweiping@didiglobal.com> wrote:
> > >
> > > If a program needs monitor lots of process's status, it needs two
> > > syscalls for every process. The first one is telling kernel which
> > > pid/tgid should be monitored by send a command(write socket) to kernel.
> > > The second one is read the statistics by read socket. This patch add
> > > a new interface /proc/taskstats to reduce two syscalls to one ioctl.
> > > The user just set the target pid/tgid to the struct taskstats.ac_pid,
> > > then kernel will collect statistics for that pid/tgid.
> > >
> > > Signed-off-by: Weiping Zhang <zhangweiping@didiglobal.com>
Could you elaborate on the overhead your seeing for the syscalls? I am not
in favour of adding new IOCTL's.
Balbir Singh.
next prev parent reply other threads:[~2021-01-27 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 17:00 Weiping Zhang
2020-12-28 14:10 ` Weiping Zhang
2021-01-22 14:07 ` Weiping Zhang
2021-01-27 11:13 ` Balbir Singh [this message]
2021-01-31 9:16 ` Weiping Zhang
2021-02-04 10:20 ` Balbir Singh
2021-02-04 14:37 ` Weiping Zhang
2021-02-05 0:08 ` Balbir Singh
2021-02-05 2:43 ` Weiping Zhang
2021-02-08 5:55 ` Balbir Singh
2021-02-10 12:30 ` Weiping Zhang
2021-02-11 2:35 ` Balbir Singh
2021-01-27 11:07 ` Balbir Singh
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=20210127111346.GB59838@balbir-desktop \
--to=bsingharora@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sblbir@amazon.com \
--cc=zwp10758@gmail.com \
/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
all inboxes | Powered by JetHome®