Re: [PATCH 2/2] __down_common: use signal_pending_state()

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Matthew Wilcox <matthew@...>
Cc: Andrew Morton <akpm@...>, Ingo Molnar <mingo@...>, Dmitry Adamushko <dmitry.adamushko@...>, Peter Zijlstra <a.p.zijlstra@...>, Roland McGrath <roland@...>, <linux-kernel@...>
Date: Wednesday, June 4, 2008 - 2:08 pm

On 06/04, Matthew Wilcox wrote:

OK.

But this was not optimisation, just code re-use.

Actually, I don't understand why __down_common/__mutex_lock_common are inlines,
perhaps it is better to shrink .text instead.

For example, "size kernel/mutex.o" reports

	2715       0      12    2727     aa7 kernel/mutex.o

with __mutex_lock_common() uninlined, we have

	1565       0      12    1577     629 kernel/mutex.o

the difference is more than K.

Oleg.

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 2/2] __down_common: use signal_pending_state(), Oleg Nesterov, (Wed Jun 4, 1:09 pm)
Re: [PATCH 2/2] __down_common: use signal_pending_state(), Matthew Wilcox, (Wed Jun 4, 1:36 pm)
Re: [PATCH 2/2] __down_common: use signal_pending_state(), Oleg Nesterov, (Wed Jun 4, 2:08 pm)
Re: [PATCH 2/2] __down_common: use signal_pending_state(), Matthew Wilcox, (Wed Jun 4, 3:54 pm)