On Tue, 29 Jan 2002, Andrew Morton wrote:
>
> And llseek is *fast*. If we're seeing significant
> lock contention in there then adding a schedule() is
> likely to turn Anton into one unhappy dbencher.
I'd agree, except I doubt there is every much contention on the _same_
file.
The reason llseek() ends up being so clear on the profiles is that it's a
very common system call under certain loads _and_ it uses a shared lock
for everything.
Also note the correctness issue (ie serialization on i_size), although
that is only an issue for SEEK_END (and maybe the lock should only be
gotten for that case. I'd love to hear what Al thinks..
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 31 2002 - 21:01:12 EST