Skip to contentSkip to conversation

2.4.10pre7aa1

DISCUSSION Maneesh Soni 2 participants 2 messages Sep 11, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines · In article <[email protected]> you wrote:

Long term of course, but with my further changes before the inclusion the plain current patches shouldn't apply any longer, I'd like if the developers of the current rcu fd patches could check my changes and adapt them (if they agree with my changes of course ;).

Hello Andrea,

I have noted your changes and I am modifying the FD patch accordingly. In fact in the first version of FD patch I have used the rc_callback() interface which equivalent to call_rcu().

Regards,
Maneesh

Signature · 6 lines
Maneesh Soni
IBM Linux Technology Center,
IBM India Software Lab, Bangalore.
Phone: +91-80-5262355 Extn. 3999
email: [email protected]
http://lse.sourceforge.net/locking/rclock.html
#1 lore raw
Quoted 7 lines · Maneesh Soni
Quoted 4 lines · In article <[email protected]> you wrote:

Long term of course, but with my further changes before the inclusion the plain current patches shouldn't apply any longer, I'd like if the developers of the current rcu fd patches could check my changes and adapt them (if they agree with my changes of course ;).

Quoted 5 lines

Hello Andrea,

I have noted your changes and I am modifying the FD patch accordingly. In fact in the first version of FD patch I have used the rc_callback() interface which equivalent to call_rcu().

many thanks. At the moment my biggest concern is about the need of call_rcu not to be starved by RT threads (keventd can be starved so then it won't matter if krcud is RT because we won't start using it). But I don't have concerns about the API so those issues will be transparent to the FD patch.

Andrea