Skip to contentSkip to conversation

realtime-preempt + reiser4?

DISCUSSION Keenan Pepper 5 participants 8 messages Jul 12, 2005 – Jul 14, 2005

lore
Share & tools
lore
#0 lore raw

Ingo Molnar's realtime-preempt patches used to be based on the -mm kernels, but now they appear to be based on the mainline kernels, so they don't support reiser4 (at least until reiser4 is merged into mainline, which is looking uncertain as I understand it). Is realtime-preempt-2.6.10-mm1-V0.7.34-01 the most recent realtime-preempt kernel to support reiser4?
How is the latency of the reiser4 code itself?

Keenan

#1 lore raw
Quoted 4 lines · Keenan Pepper

Ingo Molnar's realtime-preempt patches used to be based on the -mm kernels, but now they appear to be based on the mainline kernels, so they don't support reiser4 (at least until reiser4 is merged into mainline, which is looking uncertain as I understand it).

It's not uncertain, the reiser4 people just have to address the issues that were raised on LKML before it will be merged, just like everyone else.

Quoted 3 lines

Is realtime-preempt-2.6.10-mm1-V0.7.34-01 the most recent realtime-preempt kernel to support reiser4?
How is the latency of the reiser4 code itself?

No one ever posted any numbers (to LKML anyway) so we don't know.

Maybe you could apply the broken out reiser4 patches from -mm and the realtime preempt patches. Testing with PREEMPT_DESKTOP and latency tracing enabled will tell you whether reiser4 has any latency hot spots.

Lee

#2 lore raw
Quoted 10 lines · Lee Revell
Quoted 6 lines · Keenan Pepper

Ingo Molnar's realtime-preempt patches used to be based on the -mm kernels, but now they appear to be based on the mainline kernels, so they don't support reiser4 (at least until reiser4 is merged into mainline, which is looking uncertain as I understand it).

Quoted 5 lines

It's not uncertain, the reiser4 people just have to address the issues that were raised on LKML before it will be merged, just like everyone else.

Maybe tomorrow the changes will compile..... they have been written.....

#3 lore raw
In reply to Lee Revell
Quoted 3 lines · Lee Revell

Maybe you could apply the broken out reiser4 patches from -mm and the realtime preempt patches. Testing with PREEMPT_DESKTOP and latency tracing enabled will tell you whether reiser4 has any latency hot spots.

I'm trying this now and it's not exactly trivial; the patches conflict in some places so I had to fix by hand. Now I've got it almost compiled but it says:

fs/built-in.o: In function `kcond_wait':
: undefined reference to there_is_no_init_MUTEX_LOCKED_for_RT_semaphores' fs/built-in.o: In function kcond_timedwait':
: undefined reference to `there_is_no_init_MUTEX_LOCKED_for_RT_semaphores'

I naively changed these two calls from

init_MUTEX_LOCKED(&name);

to

init_MUTEX(&name);
down(&name);

but I'm not sure if that's right. I guess I'll see when I try to boot it!

Keenan

#4 lore raw
Quoted 2 lines · Keenan Pepper

but I'm not sure if that's right. I guess I'll see when I try to boot it!

The standard fix is to make it a compat_semaphore. See the list archives for details.

Lee

#5 lore raw
In reply to Keenan Pepper
Quoted 11 lines · Keenan Pepper

I naively changed these two calls from

init_MUTEX_LOCKED(&name);

to

init_MUTEX(&name);
down(&name);

but I'm not sure if that's right. I guess I'll see when I try to boot it!

No, since it probably wont be "uped" by the same process. So what you want to do is change the definition of name from semaphore to compat_semaphore, and keep it as init_MUTEX_LOCKED. And please send patches to Ingo (I've included him on CC). Also include Ingo on all RT related issues, since he is the one maintaining the patch.

Thanks,

-- Steve

#6 lore raw

Hello

Quoted 12 lines · Steven Rostedt
Quoted 9 lines · Keenan Pepper

I naively changed these two calls from

init_MUTEX_LOCKED(&name);

to

init_MUTEX(&name);
down(&name);

Quoted 9 lines
Quoted 1 line

but I'm not sure if that's right. I guess I'll see when I try to boot it!

No, since it probably wont be "uped" by the same process. So what you want to do is change the definition of name from semaphore to compat_semaphore, and keep it as init_MUTEX_LOCKED. And please send patches to Ingo (I've included him on CC). Also include Ingo on all RT related issues, since he is the one maintaining the patch.

ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12/reiser4-for-2.6.12-realtime-preempt-2.6.12-final-V0.7.51-29.patch.gz It applies to 2.6.12 + http://people.redhat.com/mingo/realtime-preempt/older/realtime-preempt-2.6.12-final-V0.7.51-29