Remove I/O priority. It is harmful when used with the new file code.

HAVE_IO_PRIORITY was defined for native targets with dircache.

It is already effectively disabled for the most part since dircache no
longer lowers its thread's I/O priority. It existed primarily for the
aforementioned configuration.

Change-Id: Ia04935305397ba14df34647c8ea29c2acaea92aa

1 files changed, 0 insertions, 18 deletions

diff --git a/firmware/kernel/thread.c b/firmware/kernel/thread.c
index 05c09dc594..ea76421389 100644
--- a/firmware/kernel/thread.c
+++ b/firmware/kernel/thread.c
@@ -367,10 +367,6 @@ static void new_thread_base_init(struct thread_entry *thread,
 #ifdef HAVE_SCHEDULER_BOOSTCTRL
     thread->cpu_boost = 0;
 #endif
-#ifdef HAVE_IO_PRIORITY
-    /* Default to high (foreground) priority */
-    thread->io_priority = IO_PRIORITY_IMMEDIATE;
-#endif
 }
 
 /*---------------------------------------------------------------------------
@@ -1421,20 +1417,6 @@ int thread_get_priority(unsigned int thread_id)
 }
 #endif /* HAVE_PRIORITY_SCHEDULING */
 
-#ifdef HAVE_IO_PRIORITY
-int thread_get_io_priority(unsigned int thread_id)
-{
-    struct thread_entry *thread = __thread_id_entry(thread_id);
-    return thread->io_priority;
-}
-
-void thread_set_io_priority(unsigned int thread_id,int io_priority)
-{
-    struct thread_entry *thread = __thread_id_entry(thread_id);
-    thread->io_priority = io_priority;
-}
-#endif
-
 /*---------------------------------------------------------------------------
  * Starts a frozen thread - similar semantics to wakeup_thread except that
  * the thread is on no scheduler or wakeup queue at all. It exists simply by