From: Eric Dumazet <eric.dumazet@gmail.com>
To: Venkatesh Pallipadi <venki@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org, Paul Turner <pjt@google.com>,
Shaun Ruffell <sruffell@digium.com>,
Yong Zhang <yong.zhang0@gmail.com>
Subject: Re: [PATCH 1/6] Free up pf flag PF_KSOFTIRQD
Date: Thu, 21 Oct 2010 07:23:28 +0200 [thread overview]
Message-ID: <1287638608.2545.98.camel@edumazet-laptop> (raw)
In-Reply-To: <1287614941-32325-2-git-send-email-venki@google.com>
Le mercredi 20 octobre 2010 à 15:48 -0700, Venkatesh Pallipadi a écrit :
> +int is_ksoftirqd_context(void)
> +{
> + return (current == __get_cpu_var(ksoftirqd));
> +}
"return (X == Y);" should be "return X == Y;"
I believe this function should be inlined, and use this_cpu_read()
You probably can pass 'current' as a pointer.
static inline bool is_ksoftirq(struct task_struct *p)
{
return p == this_cpu_read(ksoftirqd);
}
Your version is a bit expensive :
<is_ksoftirqd_context>:
55 push %rbp
48 89 e5 mov %rsp,%rbp
48 83 ec 10 sub $0x10,%rsp
48 89 1c 24 mov %rbx,(%rsp)
4c 89 64 24 08 mov %r12,0x8(%rsp)
48 c7 c3 40 03 01 00 mov $0x10340,%rbx
e8 93 e5 24 00 callq ffffffff812aeab0 <debug_smp_processor_id>
89 c0 mov %eax,%eax
48 8b 04 c5 a0 b8 b5 mov -0x7e4a4760(,%rax,8),%rax
81
65 4c 8b 24 25 00 cc mov %gs:0xcc00,%r12
00 00
4c 39 24 18 cmp %r12,(%rax,%rbx,1)
48 8b 1c 24 mov (%rsp),%rbx
4c 8b 64 24 08 mov 0x8(%rsp),%r12
c9 leaveq
0f 94 c0 sete %al
0f b6 c0 movzbl %al,%eax
c3 retq
While alternate version :
cmp %gs:0x10340,%rdi
(So it should be as fast as previous flag based test)
Thanks
next prev parent reply other threads:[~2010-10-21 5:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 22:48 [PATCH 0/5] Proper kernel irq time reporting -v0 Venkatesh Pallipadi
2010-10-20 22:48 ` [PATCH 1/6] Free up pf flag PF_KSOFTIRQD Venkatesh Pallipadi
2010-10-21 5:23 ` Eric Dumazet [this message]
2010-10-21 14:36 ` Venkatesh Pallipadi
2010-10-21 14:58 ` Eric Dumazet
2010-10-21 17:03 ` Venkatesh Pallipadi
2010-10-21 15:13 ` Christoph Lameter
2010-10-21 17:06 ` Venkatesh Pallipadi
2010-10-20 22:48 ` [PATCH 2/6] Add nsecs_to_cputime64 interface for asm-generic Venkatesh Pallipadi
2010-10-20 22:48 ` [PATCH 3/6] Refactor account_system_time separating id and actual update Venkatesh Pallipadi
2010-10-20 22:49 ` [PATCH 4/6] Export ns irqtimes from IRQ_TIME_ACCOUNTING through /proc/stat Venkatesh Pallipadi
2010-10-21 14:44 ` Peter Zijlstra
2010-10-21 19:25 ` Venkatesh Pallipadi
2010-10-22 12:23 ` Peter Zijlstra
2010-10-22 23:34 ` Venkatesh Pallipadi
2010-10-20 22:49 ` [PATCH 5/6] Account ksoftirq time as cpustat softirq Venkatesh Pallipadi
2010-10-21 14:53 ` Peter Zijlstra
2010-10-21 19:10 ` Venkatesh Pallipadi
2010-10-21 17:25 ` [PATCH 0/5] Proper kernel irq time reporting -v0 Shaun Ruffell
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=1287638608.2545.98.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=schwidefsky@de.ibm.com \
--cc=sruffell@digium.com \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
--cc=yong.zhang0@gmail.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