From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question on SMP and read()/write()
Date: Sat, 28 Oct 2000 17:42:50 +0200 [thread overview]
Message-ID: <00102817425009.00773@ghanima> (raw)
In-Reply-To: <Pine.LNX.4.10.10010281042130.8717-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10010281042130.8717-100000@coffee.psychology.mcmaster.ca>
On Saturday 28 October 2000 16:43, you wrote:
> > I've noticed that sys_read() and sys_write() don't grab the big kernel
> > lock. As file descriptors may be shared, must device drivers provide SMP
> > safe read() and write() methods ?
>
> no. FD's refer to files; block drivers don't, and the nontrivial
> code between sys_* and drivers deals with this sort of thing.
Sure block drivers need not do this, but how about drivers for character
devices ? It seems that sys_read() calls a function provided by the
f_op table without any locking. Isn't this the function a driver for a
character device must provide to the VFS ?
TIA
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-10-28 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10010281042130.8717-100000@coffee.psychology.mcmaster.ca>
2000-10-28 15:42 ` Oliver Neukum [this message]
2000-10-28 14:31 question on SMP and read()/write() Oliver Neukum
2000-10-28 16:19 ` Alan Cox
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=00102817425009.00773@ghanima \
--to=oliver.neukum@lrz.uni-muenchen.de \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.