From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org, xenomai@xenomai.org
Subject: [Xenomai-core] Re: [Xenomai-help] [Fwd: Performance decrease]
Date: Fri, 01 Sep 2006 20:02:15 +0200 [thread overview]
Message-ID: <1157133735.4975.14.camel@domain.hid> (raw)
In-Reply-To: <17656.19065.549422.818297@domain.hid>
On Fri, 2006-09-01 at 16:58 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > >
> > > But there is an exception: the "bind" syscall event must be intercepted
> > > for threads that are not yet marked as monitored.
> >
> > That's the major issue. We need to keep events flowing to a filtering
> > callback in order to detect binding ops, but without going through the
> > entire pipeline abstraction. And pipelining as it is now must be kept
> > for bound Linux tasks, i.e. shadows. The idea is to save the time spent
> > in the Adeos event dispatcher for tasks that don't need to tell the
> > world about what they are actually doing.
>
> The binding operation could be made a standard Linux operation, such as
> an ioctl for instance.
>
Yes. We would have to define another character device node, but since we
are going to need this for Xenomai3, we would only be anticipating the
requirement anyway.
PS: moving this discussion to xenomai-core.
--
Philippe.
prev parent reply other threads:[~2006-09-01 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 12:36 [Xenomai-help] [Fwd: Performance decrease] Philippe Gerum
2006-08-30 12:48 ` Philippe Gerum
2006-08-30 13:11 ` Jan Kiszka
2006-08-30 14:49 ` Jan Kiszka
2006-08-31 20:41 ` Gilles Chanteperdrix
2006-09-01 7:13 ` Philippe Gerum
2006-09-01 12:54 ` Gilles Chanteperdrix
2006-09-01 14:35 ` Philippe Gerum
2006-09-01 14:58 ` Gilles Chanteperdrix
2006-09-01 18:02 ` Philippe Gerum [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=1157133735.4975.14.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 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.