public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: exporting task_nice in O(1)-sched
Date: 23 Apr 2002 13:15:45 -0400	[thread overview]
Message-ID: <1019582164.1465.110.camel@phantasy> (raw)
In-Reply-To: <20020423152749.GC1697@werewolf.able.es>

On Tue, 2002-04-23 at 11:27, J.A. Magallon wrote:
 
> Found this building bproc. New O(1) scheduler kills the nice field in
> task struct. It gives a way to fix the niceness (set_user_nice()), but
> the funtion to _query_ is not exported. Any particular reason ?

Probably because Ingo intended to hide as many interfaces to the
scheduler as possible and only export those symbols that were needed.

It is safe to export if it is needed.

	Robert Love


  reply	other threads:[~2002-04-23 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 15:27 exporting task_nice in O(1)-sched J.A. Magallon
2002-04-23 17:15 ` Robert Love [this message]
2002-04-23 16:51   ` Chris Friesen

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=1019582164.1465.110.camel@phantasy \
    --to=rml@tech9.net \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox