Re: slow open() calls and o_nonblock

On 6/4/07, John Stoffel <[email protected]> wrote:

So how many files are in the directory where you're seeing the delays?
And what's the average size of the files in there?

The directories themselves will have a maximum of 160 files, and the
files are maybe a few megs each - the delays are (as you pointed out
earlier) due to the ram restrictions and our filesystem design of very
deep directory structures that Netapps suck at.

My point is more generic though - I will come up with ways to handle
this problem in my application (probably with threads), but I'm
griping more about the lack of a kernel interface that would have
allowed me to avoid this.

-Aaron
-
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/

---

• References:
  • slow open() calls and o_nonblock
    • From: "Aaron Wiebe" <[email protected]>
  • Re: slow open() calls and o_nonblock
    • From: Alan Cox <[email protected]>
  • Re: slow open() calls and o_nonblock
    • From: "Aaron Wiebe" <[email protected]>
  • Re: slow open() calls and o_nonblock
    • From: "John Stoffel" <[email protected]>

• Prev by Date: Re: slow open() calls and o_nonblock
• Next by Date: Re: [patch 1/2] ufd v1 - unsequential O(1) fdmap core
• Previous by thread: Re: slow open() calls and o_nonblock
• Next by thread: Re: slow open() calls and o_nonblock
• 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]