From: Shailabh Nagar <nagar@watson.ibm.com>
To: Jay Lan <jlan@engr.sgi.com>
Cc: Balbir Singh <balbir@in.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Chris Sturtivant <csturtiv@sgi.com>
Subject: Re: ON/OFF control of taskstats accounting data at do_exit
Date: Wed, 14 Jun 2006 23:02:26 -0400 [thread overview]
Message-ID: <4490CDC2.3090009@watson.ibm.com> (raw)
In-Reply-To: <449093D6.6000806@engr.sgi.com>
Jay Lan wrote:
>Hi Balbir and Shailabh,
>
>I propose we add the capability to turn ON/OFF the multicase of
>taskstats accounting data at do_exit().
>
>
>This would allow 'chkconfig taskstats' like of control similar
>to 'chkconfig acct' for BSD accounting. Sometimes sysadmins would
>wish to turn off sending accounting data to the multicast socket.
>We have seen many situations that our CSA customers need to turn
>off CSA for a period of time.
>
What happens to other clients listening to the data ? This sort of
configuration option would
again be along the lines of a systemwide change prompted by needs of one
subsystem but affecting
all others - something Andrew had recommended against doing while we
were discussing the per-tgid
turnoff.
The existing way to solve this is for the listeners to close the socket
and reopen again later when they
are interested. If there are no listeners at all, data won't be sent by
the kernel anyway. Won't that work
for you ?
--Shailabh
>I think this feature is very important to this new interface.
>
>Thanks,
> - jay
>
>
next prev parent reply other threads:[~2006-06-15 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 22:55 ON/OFF control of taskstats accounting data at do_exit Jay Lan
2006-06-15 3:01 ` Balbir Singh
2006-06-15 3:02 ` Shailabh Nagar [this message]
2006-06-15 3:33 ` Jay Lan
2006-06-15 14:52 ` Shailabh Nagar
2006-06-15 15:55 ` Shailabh Nagar
2006-06-15 17:24 ` Jay Lan
2006-06-15 18:14 ` Balbir Singh
2006-06-15 18:57 ` Jay Lan
2006-06-15 18:28 ` Shailabh Nagar
2006-06-15 23:41 ` Peter Williams
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=4490CDC2.3090009@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