From: Christoph Hellwig <hch@infradead.org>
To: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Cc: linux-kernel@vger.kernel.org, aris@redhat.com, jolsa@redhat.com
Subject: Re: [PATCH RFC 0/2] rlimit exceed notification events
Date: Fri, 9 Sep 2016 02:28:56 -0700 [thread overview]
Message-ID: <20160909092856.GA2874@infradead.org> (raw)
In-Reply-To: <1473244055-25240-1-git-send-email-yauheni.kaliuta@redhat.com>
On Wed, Sep 07, 2016 at 01:27:33PM +0300, Yauheni Kaliuta wrote:
> http://marc.info/?l=linux-kernel&m=147211966914100&w=2 follow up.
>
> More complete rlimits violations reporting RFC using tracing
> infrastructure.
NAK. tracepoints indtended as ABI are evil. Please use netlink
or something similar for event reporting.
prev parent reply other threads:[~2016-09-09 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 14:41 [RFC] rlimit exceed notification events Yauheni Kaliuta
2016-08-24 11:24 ` Jiri Olsa
2016-08-25 10:07 ` Yauheni Kaliuta
2016-09-07 10:27 ` [PATCH RFC 0/2] " Yauheni Kaliuta
2016-09-07 10:27 ` [PATCH RFC 1/2] rlimits: add infra to report violations Yauheni Kaliuta
2016-09-07 10:27 ` [PATCH RFC 2/2] rlimits: report resource limits violations Yauheni Kaliuta
2016-09-07 21:20 ` Alexei Starovoitov
2016-09-08 13:09 ` Hannes Frederic Sowa
2016-09-09 9:28 ` Christoph Hellwig [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=20160909092856.GA2874@infradead.org \
--to=hch@infradead.org \
--cc=aris@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yauheni.kaliuta@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.