mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Devin Heitmueller" <devin.heitmueller@gmail.com>
To: "Mauro Carvalho Chehab" <mchehab@infradead.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>, "Alan Cox" <alan@redhat.com>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] video4linux: Push down the BKL
Date: Tue, 27 May 2008 15:26:27 -0400	[thread overview]
Message-ID: <412bdbff0805271226t41fe55b0jd0b8e3c737f34734@mail.gmail.com> (raw)
In-Reply-To: <20080527155942.7693c360@gaivota>

Hello Mauro,

On Tue, May 27, 2008 at 2:59 PM, Mauro Carvalho Chehab
<mchehab@infradead.org> wrote:
> For example, em28xx has already a lock at the operations that change values at
> "dev" struct, including open() method. However, since the lock is not called at
> get operations, it needs to be fixed. I would also change it from mutex to a
> read/write semaphore, since two (or more) get operations can safely happen in
> parallel.

Please bear in mind that we have not worked out the locking semantics
for hybrid tuner devices, and it's entirely possible that the get()
routines will need to switch the tuner mode, which would eliminate any
benefits of converting to a read/write semaphore.

I'm not sure yet exactly how that's going to work, but it's something
that might prompt you to defer converting it from a mutex until we
have that worked out.

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

  reply	other threads:[~2008-05-27 19:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 21:37 Alan Cox
2008-05-23  2:08 ` Andy Walls
2008-05-23  6:16   ` Hans Verkuil
2008-05-23  6:28     ` Hans Verkuil
2008-05-26 16:39     ` Mauro Carvalho Chehab
2008-05-23  9:09   ` Alan Cox
2008-05-26 16:34     ` Mauro Carvalho Chehab
2008-05-26 16:46       ` Hans Verkuil
2008-05-26 21:14         ` Mauro Carvalho Chehab
2008-05-23 13:56 ` Jonathan Corbet
2008-05-23 15:39   ` Alan Cox
2008-05-23 16:09     ` Jonathan Corbet
2008-05-23 18:58       ` Alan Cox
2008-05-23 19:05 ` Hans Verkuil
2008-05-25 23:46 ` Mike Isely
2008-05-26 16:59 ` Mauro Carvalho Chehab
2008-05-26 20:23   ` Alan Cox
2008-05-26 21:10     ` Mauro Carvalho Chehab
2008-05-26 22:01       ` Alan Cox
2008-05-27 13:10         ` Mauro Carvalho Chehab
2008-05-27 15:41           ` Jonathan Corbet
2008-05-27 16:31             ` Mauro Carvalho Chehab
2008-05-27 16:37               ` Jonathan Corbet
2008-05-27 18:59                 ` Mauro Carvalho Chehab
2008-05-27 19:26                   ` Devin Heitmueller [this message]
2008-05-27 21:00                     ` Mauro Carvalho Chehab
2008-05-27 21:22                       ` Devin Heitmueller
2008-05-27 23:48                       ` Andy Walls
2008-05-28  0:46                         ` Devin Heitmueller
2008-05-28  2:37                           ` Andy Walls
2008-05-28  2:47                             ` Devin Heitmueller
2008-05-28  8:34                             ` Alan Cox
2008-05-28  6:13                           ` Hans Verkuil
2008-05-27 19:50                   ` Arjan van de Ven
2008-05-27 20:24                     ` Mauro Carvalho Chehab
2008-05-27 18:14               ` 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=412bdbff0805271226t41fe55b0jd0b8e3c737f34734@mail.gmail.com \
    --to=devin.heitmueller@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=video4linux-list@redhat.com \
    /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

all inboxes | Powered by JetHome®