public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Spinka, Kristofer" <kspinka@style.net>
To: linux-kernel@vger.kernel.org
Subject: Unserializing ioctl() system calls
Date: Fri, 21 May 2004 22:46:45 -0400	[thread overview]
Message-ID: <web-1649994@style.net> (raw)

I noticed that even in the 2.6.6 code, callers to ioctl 
system call (sys_ioctl in fs/ioctl.c) are serialized with 
{lock,unlock}_kernel().

I realize that many kernel modules, and POSIX for that 
matter, may not be ready to make this more concurrent.

I propose adding a flag to indicate that the underlying 
module would like to support its own concurrency 
management, and thus we avoid grabbing the BKL around the 
f_op->ioctl call.

The default behavior would adhere to existing standards, 
and if the flag is present (in the underlying module), we 
let the module (or modules) handle it.

Reasonable?

   /kristofer

             reply	other threads:[~2004-05-22  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22  2:46 Spinka, Kristofer [this message]
2004-05-22  2:54 ` Unserializing ioctl() system calls viro
2004-05-22  3:35   ` Spinka, Kristofer
     [not found] <1YuKj-2FZ-9@gated-at.bofh.it>
2004-05-22  8:03 ` Andi Kleen

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=web-1649994@style.net \
    --to=kspinka@style.net \
    --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