From: "Theodore Ts'o" <tytso@mit.edu>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Jinliang Zheng <alexjlzheng@gmail.com>,
brauner@kernel.org, jack@suse.cz, mcgrof@kernel.org,
kees@kernel.org, joel.granados@kernel.org, adobriyan@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
flyingpeng@tencent.com, Jinliang Zheng <alexjlzheng@tencent.com>
Subject: Re: [PATCH 0/6] Maintain the relative size of fs.file-max and fs.nr_open
Date: Sat, 23 Nov 2024 16:30:24 -1000 [thread overview]
Message-ID: <20241124023024.GB3874922@mit.edu> (raw)
In-Reply-To: <20241123193227.GT3387508@ZenIV>
On Sat, Nov 23, 2024 at 07:32:27PM +0000, Al Viro wrote:
>
> You won't find the words 'IO channel' in POSIX, but I refuse
> to use the term they have chosen instead - 'file description'. Yes,
> alongside with 'file descriptor', in the contexts where the distinction
> between these notions is quite important.
What I tend to do is use the term "struct file" instead. The "file
descriptor" literally is an integer index into an array of "struct
file" pointers.
"struct file" is how things are actually implemented in Linux and most
Unix systems. And while it's admittedly ugly to use an implementation
detail as an abstract term, it's infinitely less ugly than Posix's
"file description". :-)
- Ted
next prev parent reply other threads:[~2024-11-24 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 18:08 [PATCH 0/6] Maintain the relative size of fs.file-max and fs.nr_open Jinliang Zheng
2024-11-23 18:11 ` [PATCH 1/6] fs: fix proc_handler for sysctl_nr_open Jinliang Zheng
2024-11-23 18:11 ` [PATCH 2/6] fs: make files_stat globally visible Jinliang Zheng
2024-11-23 18:12 ` [PATCH 3/6] sysctl: refactor __do_proc_doulongvec_minmax() Jinliang Zheng
2024-11-23 18:12 ` [PATCH 4/6] sysctl: ensure files_stat.max_files is not less than sysctl_nr_open Jinliang Zheng
2024-11-23 18:13 ` [PATCH 5/6] sysctl: ensure sysctl_nr_open is not greater than files_stat.max_files Jinliang Zheng
2024-11-23 18:13 ` [PATCH 6/6] fs: synchronize the access of fs.file-max and fs.nr_open Jinliang Zheng
2024-11-23 18:27 ` [PATCH 0/6] Maintain the relative size " Al Viro
2024-11-23 19:32 ` Al Viro
2024-11-24 2:30 ` Theodore Ts'o [this message]
2024-11-24 9:48 ` Jinliang Zheng
2024-11-24 15:59 ` Theodore Ts'o
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=20241124023024.GB3874922@mit.edu \
--to=tytso@mit.edu \
--cc=adobriyan@gmail.com \
--cc=alexjlzheng@gmail.com \
--cc=alexjlzheng@tencent.com \
--cc=brauner@kernel.org \
--cc=flyingpeng@tencent.com \
--cc=jack@suse.cz \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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