lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7ca40f70706040724k6c5983dalcfc33ad905838bc@mail.gmail.com>
Date:	Mon, 4 Jun 2007 10:24:23 -0400
From:	"Aaron Wiebe" <epiphani@...il.com>
To:	"John Stoffel" <john@...ffel.org>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: slow open() calls and o_nonblock

On 6/4/07, John Stoffel <john@...ffel.org> 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ