All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Oxley <lkml@oxley.org>
To: "venkata jagadish.p" <cpvjagadeesh@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: Regarding RT patches
Date: Fri, 21 Oct 2005 13:33:01 +0100	[thread overview]
Message-ID: <200510211333.02214.lkml@oxley.org> (raw)
In-Reply-To: <4358B78C.2030708@gmail.com>


Hi,

I would like to (hijack) add some (newbie) questions of my own to this thread, since it has a useful title.
I hope that's OK. :-)

If there is any source of info discussing these issues on the net already please feel free to point me to it.

1.  I have seen that the testers have been carefully setting the priority of tasks so that a particular
     application comes top, followed by 1 or 2 IRQs and then maybe a hard disk etc.
     What is the effect of the RT patchset if the user takes no action to set the correct priority of their tasks?

2. Imagining that distribution X shipped with RT as configurable option defaulted to OFF, which users should
    would be advised to enable it?

3. Imagining that distribution X shipped with RT as configurable option defaulted to ON, which users should
    would be advised to disable it?

4. For completeness, that would leave certain classes of users for whom it was irrelevant/unclear whether they
   should enable/disable RT. Those classes comprising who?


Thanks,
Felix

(I hope that nobody finds it necessary to turn this thread into a flamewar. Please?  :-)






      parent reply	other threads:[~2005-10-21 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21  9:40 Regarding RT patches venkata jagadish.p
2005-10-21 12:09 ` Felix Oxley
2005-10-21 13:11   ` venkata jagadish.p
2005-10-21 12:33 ` Felix Oxley [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=200510211333.02214.lkml@oxley.org \
    --to=lkml@oxley.org \
    --cc=cpvjagadeesh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.