linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SATHISH.J" <sathish.j@tatainfotech.com>
To: linux-kernel@vger.kernel.org
Subject: Reg-directory size
Date: Thu, 14 Jun 2001 13:22:20 +0530 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10106141300430.21100-100000@blrmail> (raw)
In-Reply-To: <Pine.LNX.4.10.10106081152440.21471-100000@blrmail>

Hi,
When we create lot of files and directories under a directory the size of
the directory changes after aparticular limit. I could find that if the
size of directory is 4096 it can create 341 files(size of qstr structure
for each file is 12 bytes,so 4096/12=341.xx) before it changes to 8192. 
Please tell me where in the code does this directory size changes. Is it
in VFS level or in  the file system level? Please tell me this which would
be of great use to me.

Thanks in advance,
With Regards,
Sathish.J 


  reply	other threads:[~2001-06-14  7:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10106031716330.3971-100000@blrmail>
2001-06-04 16:34 ` Reg mkdir syscall SATHISH.J
2001-06-05  5:02   ` H. Peter Anvin
2001-06-08  6:26 ` Reg compiling of source code SATHISH.J
2001-06-14  7:52   ` SATHISH.J [this message]
2001-06-14  8:53     ` Reg-directory size Daniel Phillips
2001-06-14 10:23     ` RAM filesystem directory size SATHISH.J
2001-06-15 10:22       ` Reg file system hash function SATHISH.J
2001-06-15 10:30         ` Russell King
2001-06-17  8:06         ` Reg:dentry->d_mounts value SATHISH.J
2001-06-17  8:14           ` Reg:magic number of the filesystem SATHISH.J
2001-06-17  8:21             ` Reg:use of file_system_type structure SATHISH.J
2001-06-17  8:21               ` Alexander Viro
2001-06-18  7:56               ` function of getname() function SATHISH.J
2001-06-18  7:42                 ` Alexander Viro
2001-06-18  7:47                 ` Tigran Aivazian
2001-06-18  8:35                 ` Reg:current a pointer to task_struct SATHISH.J
2001-06-18  8:49                   ` Reg putname() function SATHISH.J
2001-06-18  9:06                   ` Reg:current a pointer to task_struct george anzinger
2001-06-20  9:41                 ` filldir() function SATHISH.J
2001-06-20 22:26                   ` Jan Kara
2001-06-25  7:11                   ` Reg Kernel Debugger kdb SATHISH.J
2001-06-25  7:33                     ` siva kumar
2001-06-25  8:36                     ` Keith Owens
2001-06-26  4:54                     ` Reg Kernel Debugger kgdb SATHISH.J
2001-06-26 10:01                       ` using gdb to debug kernel SATHISH.J
2001-06-26 10:57                         ` Lars Marowsky-Bree
2001-06-26 11:10                         ` Reg installing a patch on linux SATHISH.J
2001-06-26 16:17                     ` Reg Kernel Debugger kgdb Timur Tabi
2001-06-21 12:06               ` Reg:use of file_system_type structure Anuradha Ratnaweera
2001-06-17  8:26             ` Reg:magic number of the filesystem Alexander Viro
2001-06-11  4:59 ` exec format error SATHISH.J
2001-06-11  6:08   ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10106141300430.21100-100000@blrmail \
    --to=sathish.j@tatainfotech.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).