From: Shailabh Nagar <nagar@watson.ibm.com>
To: Shailabh Nagar <nagar@watson.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Balbir Singh <balbir@in.ibm.com>,
Jay Lan <jlan@engr.sgi.com>, Chris Sturtivant <csturtiv@sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] per-task delay accounting: avoid send without listeners
Date: Mon, 26 Jun 2006 18:33:33 -0400 [thread overview]
Message-ID: <44A060BD.6090500@watson.ibm.com> (raw)
In-Reply-To: <44A05F4F.8060503@watson.ibm.com>
Andrew,
This applies on top of the rollup of -mm (as of 5:39, 26 Jun 06), over 2.6.17,
that you have provided at
http://www.zip.com.au/~akpm/linux/patches/stuff/x.bz2
Using this and not 2.6.17-mm2 due to inclusion of other patches that aren't in -mm2.
This concludes the changes I planned to make and should hopefully address all
the overhead concerns.
Jay,
If there are any remaining overhead issues you see, pls let me know asap.
Thanks,
Shailabh
Shailabh Nagar wrote:
> Don't send taskstats (per-pid or per-tgid) on thread exit when no one is
> listening for such data.
>
> Currently the taskstats interface allocates a structure, fills it in
> and calls netlink to send out per-pid and per-tgid stats regardless of whether
> a userspace listener for the data exists (netlink layer would check for that
> and avoid the multicast).
>
> As a result of this patch, the check for the no-listener case is performed
> early, avoiding the redundant allocation and filling up of the taskstats
> structures.
>
> Signed-off-by: Balbir Singh <balbir@in.ibm.com>
> Signed-off-by: Shailabh Nagar <nagar@watson.ibm.com>
prev parent reply other threads:[~2006-06-26 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 22:27 [RFC][PATCH] per-task delay accounting: avoid send without listeners Shailabh Nagar
2006-06-26 22:33 ` Shailabh Nagar [this message]
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=44A060BD.6090500@watson.ibm.com \
--to=nagar@watson.ibm.com \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=csturtiv@sgi.com \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.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