[New-bugs-announce] [issue40423] Optimization: use close_range(2) if available

[Kyle Evans]

New submission from Kyle Evans <kevans at FreeBSD.org>:

This is dependent on issue40422; the diff on top of that (PR19075) looks like the attached. Effectively, close_range(2) should be preferred at all times if it's available, otherwise we'll use closefrom(2) if available with a fallback to fdwalk(3) or plain old loop over fd range in order of most efficient to least.

PR will be sent after issue40422 is resolved.

----------
components: C API
files: cpython-close_range.diff
keywords: patch
messages: 367531
nosy: kevans91
priority: normal
severity: normal
status: open
title: Optimization: use close_range(2) if available
type: enhancement
versions: Python 3.9
Added file: https://bugs.python.org/file49097/cpython-close_range.diff

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue40423>
_______________________________________