From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, matthew@wil.cx
Subject: Re: [PATCH] Remove argument from open_softirq which is always NULL
Date: Fri, 16 May 2008 16:52:23 -0300 [thread overview]
Message-ID: <20080516195223.GA5308@beyonder.ift.unesp.br> (raw)
In-Reply-To: <20080516182807.GA28406@linux.vnet.ibm.com>
On Fri 16.May'08 at 11:28:07 -0700, Paul E. McKenney wrote:
> On Thu, May 15, 2008 at 11:15:37AM -0300, Carlos R. Mafra wrote:
> > From 9371c45e92c308425c0aad4794f61acb6fe6d140 Mon Sep 17 00:00:00 2001
> > From: Carlos R. Mafra <crmafra@ift.unesp.br>
> > Date: Wed, 14 May 2008 18:26:06 -0300
> > Subject: [PATCH] Remove argument from open_softirq which is always NULL
> >
> > As git-grep shows, open_softirq() is always called with the last argument
> > being NULL
> >
> > block/blk-core.c: open_softirq(BLOCK_SOFTIRQ, blk_done_softirq, NULL);
> > kernel/hrtimer.c: open_softirq(HRTIMER_SOFTIRQ, run_hrtimer_softirq, NULL);
> > kernel/rcuclassic.c: open_softirq(RCU_SOFTIRQ, rcu_process_callbacks, NULL);
> > kernel/rcupreempt.c: open_softirq(RCU_SOFTIRQ, rcu_process_callbacks, NULL);
> > kernel/sched.c: open_softirq(SCHED_SOFTIRQ, run_rebalance_domains, NULL);
> > kernel/softirq.c: open_softirq(TASKLET_SOFTIRQ, tasklet_action, NULL);
> > kernel/softirq.c: open_softirq(HI_SOFTIRQ, tasklet_hi_action, NULL);
> > kernel/timer.c: open_softirq(TIMER_SOFTIRQ, run_timer_softirq, NULL);
> > net/core/dev.c: open_softirq(NET_TX_SOFTIRQ, net_tx_action, NULL);
> > net/core/dev.c: open_softirq(NET_RX_SOFTIRQ, net_rx_action, NULL);
> >
> > This observation has already been made by Matthew Wilcox in June 2002
> > (http://www.cs.helsinki.fi/linux/linux-kernel/2002-25/0687.html)
> >
> > "I notice that none of the current softirq routines use the data element
> > passed to them."
> >
> > and the situation hasn't changed since them. So it appears we can safely
> > remove that extra argument to save 128 (54) bytes of kernel data (text).
>
> Good stuff!!!
Thanks a lot!
> Will there also be a similar set of patches that removes the extra
> argument from the invoked function? For example:
>
> static void rcu_process_callbacks(struct softirq_action *unused)
>
> could now become:
>
> static void rcu_process_callbacks(void)
That was my intention at first when I came acroos
run_hrtimer_softirq(struct softirq_action *h) in hrtimer.c, which then led me to
read more code and notice that I could do the cleanup in this patch.
You've just gave me the motivation I needed to keep cleaning (and learning) further,
as the original bug which motivated me to look at those things does not
happen anymore in my laptop :-)
I will try to do another patch soon, but I will travel tomorrow so it
may take a few days.
> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Thanks,
Carlos
next prev parent reply other threads:[~2008-05-16 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:15 Carlos R. Mafra
2008-05-15 15:22 ` Matthew Wilcox
2008-05-16 11:57 ` Ingo Molnar
2008-05-16 18:28 ` Paul E. McKenney
2008-05-16 19:52 ` Carlos R. Mafra [this message]
2008-05-17 4:24 ` [PATCH] Remove unused argument from functions invoked by open_softirq Carlos R. Mafra
2008-05-17 6:03 ` Paul E. McKenney
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=20080516195223.GA5308@beyonder.ift.unesp.br \
--to=crmafra2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulmck@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®