Skip to contentSkip to conversation

slowdown with new scheduler.

DISCUSSION Dieter Nützel 3 participants 3 messages Jan 14, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Dieter Nützel

author
#1 lore raw
Quoted 16 lines · you
Quoted 15 lines · Heinz Diehl
Quoted 12 lines · Heinz Diehl
2.4.18-pre3             real    7m55.243s
                        user    6m34.080s
                        sys     0m27.610s
2.4.18-pre+H7                   real    7m35.962s
                        user    6m34.270s
                        sys     0m27.700s
2.4.18-pre3-ac2         real    7m39.203s
                        user    6m34.110s
                        sys     0m28.740s
Quoted 6 lines
Quoted 4 lines

2.4.18-pre3+H7+preempt-rml real 6m58.983s

                          user    6m34.500s
                          sys     0m27.820s

That sounds very good! But what about the VM code? Is the VM in 2.4.18-pre3+H7 as good as in 2.4.18-pre2aa2?

Of course _NOT_.
This is like apples and oranges...

You _must_ compare
2.4.18-pre3+H7+ -aa vm-22 from 2.4.18-pre2aa2
with
2.4.18-pre3+H7+ -rmap

After that you should apply preempt+locl-break or LL to both.

Have a look into Re: [2.4.17/18pre] VM and swap - it's really unusable

Greetings,
Dieter

Signature · 6 lines
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
@home: [email protected]
#2 lore raw
In reply to a message not in the archive
Quoted 4 lines · Dieter Nützel

You _must_ compare
2.4.18-pre3+H7+ -aa vm-22 from 2.4.18-pre2aa2
with
2.4.18-pre3+H7+ -rmap

This is not possible for me since rmap-11b does not apply cleanly to 2.4.18-pre3+H7, several hunks fail. I'm not a programmer, so I'm not able to make the patches fit together.

Quoted 1 line

After that you should apply preempt+locl-break or LL to both.

The same here, lock-break does not apply to 2.4.18-pre3+H7 without some failed hunks....

Signature · 1 line
# Heinz Diehl, 68259 Mannheim, Germany
#3 lore raw
Quoted 4 lines · Heinz Diehl
Quoted 1 line

After that you should apply preempt+locl-break or LL to both.

The same here, lock-break does not apply to 2.4.18-pre3+H7 without some failed hunks....

Just a note, if lock-break fails in chunks it is probably OK to just ignore them. Each lock-break is independent so, while it is less lock breaking, it is nearly the same and certainly works fine.

Wouldn't give the same advice for rmap, however. Best to make sure your VM applies cleanly :)

Robert Love