Re: [patch 2/9] Conditional Calls - Hash Table

Mathieu Desnoyers <[email protected]> writes:

> Reimplementation of the cond calls which uses a hash table to hold the active
> cond_calls. It permits to first arm a cond_call and then load supplementary
> modules that contain this cond_call.

Hash table is probably overkill. This is a very very slow path operation.
Can you simplify the code? Just a linked list of all the condcall segments
should be enough  and then walk it.

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

---

• Follow-Ups:
  • Re: [patch 2/9] Conditional Calls - Hash Table
    • From: Matt Mackall <[email protected]>

• References:
  • [patch 0/9] Conditional Calls - for 2.6.22-rc2-mm1
    • From: Mathieu Desnoyers <[email protected]>
  • [patch 2/9] Conditional Calls - Hash Table
    • From: Mathieu Desnoyers <[email protected]>

• Prev by Date: Re: [patch 9/9] Scheduler profiling - Use conditional calls
• Next by Date: Re: Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards. (FULL DMESG)
• Previous by thread: Re: [patch 2/9] Conditional Calls - Hash Table
• Next by thread: Re: [patch 2/9] Conditional Calls - Hash Table
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]