From: Dirk Behme <dirk.behme@googlemail.com>
To: Jaswinder Singh <jaswinderlinuxrt@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: FAQ for realtime support in Linux Kernel
Date: Sat, 29 Sep 2007 07:11:03 +0200 [thread overview]
Message-ID: <46FDDE67.1030507@googlemail.com> (raw)
In-Reply-To: <1985e0f60709282200q46af6416v1df50da135d5d01c@mail.gmail.com>
Jaswinder Singh wrote:
> I need your help and guidance to make this FAQ.
>
> Please send some links, data and reviews which will be useful for this FAQ.
Did you read stuff and links on
http://rt.wiki.kernel.org/index.php/Main_Page
?
I think at least some of your questions below should be answered there.
If anything is missing, feel free to add it. And, if you like, I would
propose to create a new FAQ page in above wiki and collect your
answers there.
Best regards
Dirk
> Thanks you,
>
> Jaswinder Singh.
>
> Question Index
> ----------------------
> 1. What is realtime support
>
> 2. How realtime works
>
> 3. What is the procedure to add realtime support
>
> 4. Download latest realtime patches
>
> 5. Realtime mailing list and archives
>
> 6. If I have some doubts or problems regarding realtime, do I need to
> send mail in realtime mailing list or linux kernel mailing list or
> both
>
> 7. Maintainers of realtime kernel patch
>
> 8. How to enable/disable realtime support
>
> 9. Change realtime support run time or statically
>
> 10. Required parameters for configuring realtime kernel
>
> 11. Optional parameters for configuring realtime kernel, but they
> effect realtime performance
>
> 12. Which Architecture are supporting realtime and who is maintainer
>
> 13. What effects by realtime support and how much and samples to test
> it and who maintains these samples
>
> a. scheduling, task switching time
>
> b. Interrupt latency
>
> c. Interprocess communication
>
> d. Filesystem
>
> e. Device drivers
>
> f. Network
>
> g. X-Windows
>
>
> 14. List of realtime APIs
>
> 15. How to write realtime applications
>
> 16. Which programming languages are suitable for writing realtime applications
>
> 17. Keep following things in mind while writing realtime applications
>
> 18. Do I need to recompile my applications to get realtime performance
>
> 19. What is the procedure to support realtime in new architecture
>
> 20. Where can I post my realtime patches
> -
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-09-29 5:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 5:00 FAQ for realtime support in Linux Kernel Jaswinder Singh
2007-09-29 5:11 ` Dirk Behme [this message]
2007-09-29 5:29 ` Jaswinder Singh
2007-09-29 6:44 ` Jaswinder Singh
2007-09-29 9:39 ` Esben Nielsen
2007-09-29 12:51 ` Jaswinder Singh
2007-09-29 13:13 ` Luis Claudio R. Goncalves
2007-09-29 15:16 ` Jaswinder Singh
2007-09-29 16:56 ` Theodore Tso
2007-09-29 17:18 ` Jaswinder Singh
2007-09-30 5:56 ` Jaswinder Singh
2007-10-01 11:04 ` Jaswinder Singh
2007-10-01 20:18 ` Remy Bohmer
2007-10-02 0:02 ` Theodore Tso
2007-10-02 1:41 ` Jaswinder Singh
2007-10-02 3:39 ` Girish kathalagiri
2007-10-02 15:35 ` Remy Bohmer
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=46FDDE67.1030507@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=jaswinderlinuxrt@gmail.com \
--cc=linux-rt-users@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 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.