All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@wildopensource.com>
To: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: rename the ksoftirqd kernel thread.
Date: Thu, 15 May 2003 17:17:16 -0400	[thread overview]
Message-ID: <20030515211716.GV17021@bork.org> (raw)


Marcelo,

Please consider this patch for 2.4.22-pre

It just renames the ksoftirqd kernel thread to be the same as in 2.5.

The side effect is that on machines with > 100 processors the last
number in the thread name doesn't get truncated.  

The patch is against linux-2.4 bk.

thanks
mh

-- 
Wild Open Source Inc.                  mort@wildopensource.com


# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1210  -> 1.1211 
#	    kernel/softirq.c	1.11    -> 1.12   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/05/15	mort@plato.i.bork.org	1.1211
# Rename the ksoftirqd thread to be the same as in 2.5.
# --------------------------------------------
#
diff -Nru a/kernel/softirq.c b/kernel/softirq.c
--- a/kernel/softirq.c	Thu May 15 17:13:08 2003
+++ b/kernel/softirq.c	Thu May 15 17:13:08 2003
@@ -372,7 +372,7 @@
 	while (smp_processor_id() != cpu)
 		schedule();
 
-	sprintf(current->comm, "ksoftirqd_CPU%d", bind_cpu);
+	sprintf(current->comm, "ksoftirqd/%d", bind_cpu);
 
 	__set_current_state(TASK_INTERRUPTIBLE);
 	mb();

             reply	other threads:[~2003-05-15 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 21:17 Martin Hicks [this message]
2003-05-15 21:51 ` rename the ksoftirqd kernel thread J.A. Magallon
2003-05-16 12:41   ` Martin Hicks

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=20030515211716.GV17021@bork.org \
    --to=mort@wildopensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.