From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Changli Gao <xiaosuo@gmail.com>
Cc: "netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Jan Engelhardt <jengelh@medozas.de>
Subject: Re: [RFC] setting up throughput threshold indications to userspace
Date: Mon, 16 Aug 2010 17:32:42 +0300 [thread overview]
Message-ID: <1281969162.27200.45.camel@chilepepper> (raw)
In-Reply-To: <AANLkTikxcG8GpTTE5h28QSjD2uXpPXdNwFrshn2UKQRY@mail.gmail.com>
On Mon, 2010-08-16 at 16:26 +0200, ext Changli Gao wrote:
> On Mon, Aug 16, 2010 at 9:40 PM, Luciano Coelho
> <luciano.coelho@nokia.com> wrote:
> > Does anyone have an idea on how I could solve this problem?
> >
> > I have been considering using the IDLETIMER target and activate it when
> > the throughput goes to HIGH. Then if this timer expires, it would
> > inform the userspace that now there's no data going through. But this
> > sounds very artificial to me and will add one more dependency on the
> > userspace, since the IDLETIMER is using sysfs to inform userspace,
> > instead of netlink.
> >
>
> Read the code of IDLETIMER again, and I notice that IDLETIMER will
> wake up all the sleepers on the corresponding sysfs files. So no
> polling is needed, what you need do is watching another files for
> read. You can use select/poll/epoll. It should be no very difficult.
Yes, I know. I have reworked the IDLETIMER for upstream inclusion, so I
should know this after all. ;) It was just the idea of having the daemon
have one more interface with the kernel that seemed a bit ugly...
--
Cheers,
Luca.
prev parent reply other threads:[~2010-08-16 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 8:20 [RFC] setting up throughput threshold indications to userspace Luciano Coelho
2010-07-16 13:01 ` Patrick McHardy
2010-07-16 13:10 ` Luciano Coelho
2010-07-16 19:27 ` Jan Engelhardt
2010-07-19 5:30 ` Luciano Coelho
2010-08-16 13:40 ` Luciano Coelho
2010-08-16 13:51 ` Changli Gao
2010-08-16 14:01 ` Luciano Coelho
2010-08-16 14:13 ` Changli Gao
2010-08-16 14:26 ` Luciano Coelho
2010-08-16 15:19 ` Jan Engelhardt
2010-08-17 5:27 ` Luciano Coelho
2010-08-16 14:26 ` Changli Gao
2010-08-16 14:32 ` Luciano Coelho [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=1281969162.27200.45.camel@chilepepper \
--to=luciano.coelho@nokia.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sameo@linux.intel.com \
--cc=xiaosuo@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;
as well as URLs for NNTP newsgroup(s).