From: Oleg Nesterov <oleg@redhat•com>
To: Christian Brauner <christian@brauner•io>
Cc: linux-ia64@vger•kernel.org, linux-sh@vger•kernel.org,
ldv@altlinux•org, dhowells@redhat•com,
linux-kselftest@vger•kernel.org, sparclinux@vger•kernel.org,
shuah@kernel•org, linux-arch@vger•kernel.org,
linux-s390@vger•kernel.org, miklos@szeredi•hu, x86@kernel•org,
torvalds@linux-foundation•org, linux-mips@vger•kernel.org,
linux-xtensa@linux-xtensa•org, tkjos@android•com, arnd@arndb•de,
jannh@google•com, linux-m68k@lists•linux-m68k.org,
viro@zeniv•linux.org.uk, tglx@linutronix•de,
linux-arm-kernel@lists•infradead.org, fweimer@redhat•com,
linux-parisc@vger•kernel.org, linux-api@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-alpha@vger•kernel.org,
linux-fsdevel@vger•kernel.org, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH v1 1/2] open: add close_range()
Date: Thu, 23 May 2019 18:21:04 +0200 [thread overview]
Message-ID: <20190523162104.GD23070@redhat.com> (raw)
In-Reply-To: <20190523142826.omb7vgygudifmveq@brauner.io>
On 05/23, Christian Brauner wrote:
>
> So given that we would really need another find_next_open_fd() I think
> sticking to the simple cond_resched() version I sent before is better
> for now until we see real-world performance issues.
OK, agreed.
Oleg.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-23 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 15:52 [PATCH v1 1/2] open: add close_range() Christian Brauner
2019-05-22 15:52 ` [PATCH v1 2/2] tests: add close_range() tests Christian Brauner
2019-05-22 16:57 ` [PATCH v1 1/2] open: add close_range() Oleg Nesterov
2019-05-23 11:51 ` Christian Brauner
2019-05-23 14:14 ` Christian Brauner
2019-05-23 14:28 ` Christian Brauner
2019-05-23 16:21 ` Oleg Nesterov [this message]
2019-05-23 14:32 ` Jann Horn
2019-05-23 14:37 ` Christian Brauner
2019-05-23 16:22 ` Konstantin Khlebnikov
2019-05-23 16:29 ` David Laight
2019-05-23 16:33 ` Christian Brauner
2019-05-24 7:43 ` Arnd Bergmann
2019-05-24 9:57 ` Christian Brauner
2019-05-24 10:31 ` Christian Brauner
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=20190523162104.GD23070@redhat.com \
--to=oleg@redhat$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=christian@brauner$(echo .)io \
--cc=dhowells@redhat$(echo .)com \
--cc=fweimer@redhat$(echo .)com \
--cc=jannh@google$(echo .)com \
--cc=ldv@altlinux$(echo .)org \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-api@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-m68k@lists$(echo .)linux-m68k.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linux-xtensa@linux-xtensa$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=miklos@szeredi$(echo .)hu \
--cc=shuah@kernel$(echo .)org \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tglx@linutronix$(echo .)de \
--cc=tkjos@android$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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