linux-kernel - How does RCU work?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080805.000943.208968239.takada@mbf.nifty.com>
Date:	Tue, 05 Aug 2008 00:09:43 +0900 (JST)
From:	TAKADA Yoshihito <takada@....nifty.com>
To:	linux-kernel@...r.kernel.org
Subject: How does RCU work?

Hi.
I cannot understand mechanism. Somebody tell me it please.

In x86 kernel, CONFIG_PREEMPT_RCU=n (CONFIG_CLASSIC_RCU=y). rcu_read_lock() makes
just preempt_disable().
call_cru()/synchronize_rcu() running as a soft-IRQ.
It's current CPU does not refer to protected data that when call_rcu() run. 
Because soft-IRQ handler ran, it means current CPU is preempive. That is the CPU
called rcu_read_unlock().

Well, current CPU is unlocked, but How does kernel know it other CPUs unlocked?

call_ruc() calls force_quiescent_state() to reschedule other CPUs. 
force_quiescent_state() calls smp_send_reschedule() to sends request to reshecule.
It's just require to reschedule via inter Processor Interrupt. But call_rcu() does
not wait for target CPUs handle IPI. Or, Do CPUs have it handled IPI request when
return from smp_send_reschedule()?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/