On 11/20/2011 03:26 PM, H. Peter Anvin wrote:
On 11/18/2011 11:37 AM, David Daney wrote:
From: David Daney<david.daney@xxxxxxxxxx>
Using this build-time sort saves time booting as we don't have to burn
cycles sorting the exception table.
If we're going to do this at build time, I would suggest using a
collisionless hash instead. The lookup time for those are O(1), but
they definitely need to be done at build time.
It is my understanding that such a hash table would be sparsely
populated, so space would have to be reserved for the empty buckets.
The current patch, which works in-place on the fully linked vmlinux,
doesn't have to worry about finding enough space for the table.
If we were to do the collisionless hash, we would somehow have to
reserve space for the empty buckets.
On my test kernel, there were only 1453 entries in the exception table,
So doing the binary search takes a maximum of 11 loads.
So, I guess I am not strongly opposed to using a collisionless hash, but
I think it may not be worth the extra effort.
David Daney
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html