public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Anjali Kulkarni <anjali.k.kulkarni@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] Add a new generic system call which has better performance, to get /proc data, than existing mechanisms
Date: Thu, 17 Nov 2022 22:38:36 +0100	[thread overview]
Message-ID: <Y3ap3KjiMEAF39t7@kroah.com> (raw)
In-Reply-To: <1668623844-9114-1-git-send-email-anjali.k.kulkarni@oracle.com>

On Wed, Nov 16, 2022 at 10:37:24AM -0800, Anjali Kulkarni wrote:
> Currently, reading from /proc is an expensive operation, for a
> performance sensitive application

Then perhaps "performance sensitive applications" should not be reading
10's of thousands of /proc files?

Anyway, your proposal comes up every few years, in different ways.
Please research the past proposals for why this keeps failing and
perhaps you should just fix up your userspace code instead?

Also, look at attempts like the introduction of the readfile syscall as
well, if you want to remove the open/read/close set of syscalls into
one, but even that isn't all that useful for real-world applications, as
you can today use the io_uring api to achieve almost the same throughput
if really needed.

good luck!

greg k-h

  reply	other threads:[~2022-11-17 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 18:37 [RFC] Add a new generic system call which has better performance, to get /proc data, than existing mechanisms Anjali Kulkarni
2022-11-17 21:38 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-18 19:10 Anjali Kulkarni
2022-11-18 19:12 Anjali Kulkarni
2022-11-19  8:49 ` Greg KH
     [not found]   ` <MN2PR10MB414411D0E29F20412E6DF0C0C4089@MN2PR10MB4144.namprd10.prod.outlook.com>
2022-11-20  8:21     ` Greg KH
2022-11-20 19:37       ` Anjali Kulkarni
2022-11-21 18:28       ` Anjali Kulkarni

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=Y3ap3KjiMEAF39t7@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anjali.k.kulkarni@oracle.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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