From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jeff Webb <jeff.webb@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] the same error-solution
Date: Wed, 15 Mar 2006 17:50:21 +0100 [thread overview]
Message-ID: <441845CD.8010102@domain.hid> (raw)
In-Reply-To: <44184158.8010805@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]
Jeff Webb wrote:
> marcellin wrote:
>> -I've forgot rt_task_shadow() in the main Linux thread
>
> It would be helpful to add a note to the API docs for rt_task_shadow()
> explaining this usage. It would also be good to note that tasks created
> in this way must also be cleaned up using rt_task_delete().
>
> rt_task_shadow()
> -----
> Turns the current Linux task into a native Xenomai task. Creates a
> real-time task running in the context of the calling regular Linux task
> in user-space. For instance, calling rt_task_shadow() from main() will
> map the program's main thread to a native Xenomai thread, allowing it to
> invoke blocking real-time services. Note that all tasks created using
> rt_task_shadow() must be cleaned up using rt_task_delete().
> -----
Oops, this need for cleanup likely dates back to my comment It's
actually not that hard. The related kernel resources get released when
the task terminates. But cleanup is (still) mandatory for non-task objects.
>
> It would be good to put a note in the rt_task_delete() docs as well.
>
> rt_task_delete()
> -----
> ... A task exists in the system since rt_task_create() ( or possibly
> rt_task_shadow() ) has been called to create it, so this service must be
> called in order to destroy it afterwards...
> -----
>
> I'm sure these comments are obvious to many folks, but it would help out
> the newbies. It is helpful when the documentation explicitly says
> things like this, so one doesn't have to guess.
>
> Thanks again for putting in the effort to make great API documentation.
> I believe it is essential to the widespread adoption of Xenomai, and
> makes it very attractive to the newcomer.
>
> If you would rather have me submit suggestions like this in patch form,
> I would be happy to do so. Just show me an example diff (or 'svn
> diff'?) command so I know what command-line options you prefer.
Yes, svn diff gives very good output. And yes, a patch is even more
welcome than your already helpful comments. I recently learned again
that RTDM is also still suffering from inherent but undocumented
characteristics, things that are obvious - at least for me. ;)
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-03-15 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 14:00 [Xenomai-help] the same error marcellin
2006-03-14 14:13 ` Gilles Chanteperdrix
2006-03-14 14:42 ` marcellin
2006-03-14 15:53 ` Gilles Chanteperdrix
2006-03-15 7:35 ` [Xenomai-help] the same error-solution marcellin
2006-03-15 16:31 ` Jeff Webb
2006-03-15 16:50 ` Jan Kiszka [this message]
2006-03-14 14:28 ` [Xenomai-help] the same error Jan Kiszka
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=441845CD.8010102@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=jeff.webb@domain.hid \
--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.