Skip to contentSkip to conversation

2.4.23aa2 (bugfixes and important VM improvements for the high end)

DISCUSSION Andi Kleen 2 participants 3 messages Mar 7, 2004 – Mar 18, 2004 17 messages 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]

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

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

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

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

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

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

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

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

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

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

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

Andi Kleen

author
#12 lore raw
Quoted 3 lines · Peter Zaitsev

Rather than changing design how time is computed I think we would better to go to better accuracy - nowadays 1 second is far too raw.

Just call gettimeofday(). In near all kernels time internally does that anyways.

-Andi

#13 lore raw
Quoted 7 lines · Andi Kleen
Quoted 3 lines · Peter Zaitsev

Rather than changing design how time is computed I think we would better to go to better accuracy - nowadays 1 second is far too raw.

Just call gettimeofday(). In near all kernels time internally does that anyways.

Right,

gettimeofday() was much slower some years ago on some other Unix Platform, which is why time() was used instead.

Now we just need to fix a lot of places (datatypes, prints etc) to move to gettimeofday()

Signature · 5 lines
Peter Zaitsev, Senior Support Engineer
MySQL AB, www.mysql.com

Meet the MySQL Team at User Conference 2004! (April 14-16, Orlando,FL)
  http://www.mysql.com/uc2004/

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

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

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

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

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

author
#19 lore raw
Quoted 5 lines · Ingo Molnar

but i'm quite strongly convinced that 'getting rid' of the 'pte chain overhead' in favor of questionable lowmem space gains for a dying (high-end server) platform is very shortsighted. [getting rid of them for purposes of the 64-bit platforms could be OK, but the argumentation isnt that strong there i think.]

pte chain locking seems to be still quite far up in profile logs of 2.6 on x86-64 for common workloads. It's nonexistent in mainline 2.4. I would consider this a strong reason to do something about that.

-Andi