On 10 Jun 2008, at 16:14, Ciaran McCreesh wrote:
On Tue, 10 Jun 2008 19:38:52 +0530
"Arun Raghavan" <[EMAIL PROTECTED]> wrote:
On Tue, Jun 10, 2008 at 7:30 PM, Ciaran McCreesh
<[EMAIL PROTECTED]> wrote:
[...]
- it doubles the number of file reads necessary during resolution.
The first read will cause the file to be cached for subsequent reads
anyway, so the performance hit boils down to an additional read()
call
(which will probably be buffered by your file I/O library anyway, so
it's unlikely to even result in a context switch). And even without,
it is well worth the lack of fugliness in the ebuild name.
No, it results in a new open() on a file that's elsewhere on disk,
which
results in two new seeks. You get about fifty seeks per second.
Plus path resolution, which isn't exactly free
- ferdy
--
[email protected] mailing list
