Robin Holt <[email protected]> wrote:
>
> Let me reiterate, I know _VERY_ little about filesystems. Can the
> dentry->d_lock be changed to a read/write lock?
Well, it could, but I suspect that won't help - the hold times in there
will be very short so the problem is more likely acquisition frequency.
However it's a bit strange that this function is the bottleneck. If their
workload is doing large numbers of reads or writes from large numbers of
processes against the same file then they should be hitting heavy
contention on other locks, such as i_sem and/or tree_lock and/or lru_lock
and others.
Can you tell us more about the kernel-visible behaviour of this app?
-
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/
[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]
