From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Is vnode number also limit system-wide number of open file?
Date: Wed, 31 May 2017 13:30:59 -0400 [thread overview]
Message-ID: <1496251859.29205.90.camel@surriel.com> (raw)
In-Reply-To: <20170531133754.GA9534@HP>
On Wed, 2017-05-31 at 21:37 +0800, Yubin Ruan wrote:
> I notice that there is a?
> ????
> unsigned long i_ino;
>
> in definition of `struct inode' [1], which is the virtual filesystem
> inode.
> Does that mean "inode number" and is it used for indexing in the
> system-wide
> inode table??
>
> If that is the case, would that limit the number of open file in
> Linux?
Those numbers are unrelated.
The i_ino number is the inode number within each
filesystem, and different filesystems can have
inodes with the same inode numbers.
File descriptors (open files) point to a struct inode
somewhere in memory. The same file can be opened many
times (all programs opening libc.so). Many files will
not be opened by any program at all.
--
All Rights Reversed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170531/e88422ec/attachment.bin
next prev parent reply other threads:[~2017-05-31 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 13:37 Is vnode number also limit system-wide number of open file? Yubin Ruan
2017-05-31 7:34 ` Okash Khawaja
2017-05-31 17:47 ` Yubin Ruan
2017-05-31 17:30 ` Rik van Riel [this message]
2017-06-01 9:15 ` Yubin Ruan
2017-06-01 2:12 ` valdis.kletnieks at vt.edu
2017-06-01 2:16 ` Manish Katiyar
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=1496251859.29205.90.camel@surriel.com \
--to=riel@surriel.com \
--cc=kernelnewbies@lists.kernelnewbies.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).