public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Adrian McMenamin <lkmladrian@gmail.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] SH/Dreamcast - add support for GD-Rom device
Date: Thu, 27 Dec 2007 12:49:39 +0000	[thread overview]
Message-ID: <1198759779.6170.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20071227081822.GA22693@linux-sh.org>


On Thu, 2007-12-27 at 17:18 +0900, Paul Mundt wrote:
> On Thu, Dec 27, 2007 at 01:26:47AM +0000, Adrian McMenamin wrote:

> 
> > +		/* now seek to take the request spinlock
> > + 		 * before handling ending the request */
> > +		spin_lock(&gdrom_lock);
> > +		list_del_init(&req->queuelist);
> > +		blk_requeue_request(gd.gdrom_rq, req);
> > +		if (err)
> > +			end_request(req, 0);
> > +		else
> > +			end_request(req, 1);
> > +	}
> > +	spin_unlock(&gdrom_lock);
> > +	kfree(read_command);
> > +}	
> > +
> This locking is all over the place. What is this lock supposed to be
> accomplishing?
> -

I have to hold the lock to access the request queue. As the linked list
of deferred requests is under the control of code also protected by the
lock, it is also held to ensure manipulation of that list is serialised.

The first step of the loop manipulates that linked list - so it is held
as we re-iterate over the loop.

This is pretty much the way Jens recommended I do it.


  reply	other threads:[~2007-12-27 12:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27  1:26 [PATCH] SH/Dreamcast - add support for GD-Rom device Adrian McMenamin
2007-12-27  8:18 ` Paul Mundt
2007-12-27 12:49   ` Adrian McMenamin [this message]
2007-12-27 19:52     ` Jens Axboe
2007-12-27 19:11   ` Mike Frysinger
2007-12-27 16:52 ` Adrian McMenamin
2007-12-27 20:56   ` Adrian McMenamin
2007-12-27 22:20   ` Paul Mundt
2007-12-27 22:58   ` Joe Perches
2007-12-28  0:18     ` Simon Holm Thøgersen
2007-12-29  1:57       ` Joe Perches
2007-12-29 12:03         ` Adrian McMenamin
2007-12-29 12:10           ` Adrian McMenamin
2007-12-29 18:07           ` Joe Perches
2007-12-28  0:49     ` Mike Frysinger
2007-12-28  3:41       ` Paul Mundt
2007-12-28 19:17     ` Gino Badouri
2007-12-28 22:09       ` Joe Perches
2007-12-30 13:38     ` Adrian McMenamin
2007-12-31  5:23       ` Paul Mundt
2008-01-10 23:25 ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Adrian McMenamin
2008-01-11 21:56   ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on Adrian McMenamin
2008-01-12 11:57     ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Dreamcast Jens Axboe
2008-01-12 13:36     ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on Andrew Morton
2008-01-12 14:14       ` Adrian McMenamin
2008-01-12 19:15         ` Andrew Morton
2008-01-13 18:24           ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Dreamcast Adrian McMenamin
2008-01-14 23:00       ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on Adrian McMenamin
2008-01-14 23:17         ` Adrian McMenamin
2008-01-15  0:29           ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Dreamcast Paul Mundt
2008-01-15 20:41             ` Adrian McMenamin
2008-01-16 23:57           ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on Adrian McMenamin
2008-01-17  1:27             ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Dreamcast Paul Mundt
2008-01-17 22:30               ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on Adrian McMenamin
2008-01-18  0:56                 ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Dreamcast Paul Mundt
2008-01-28  5:33                   ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on Andrew Morton
2008-01-28  5:53                     ` [PATCH] SH/Dreamcast - add support for GD-Rom CDROM drive on SEGA Dreamcast Paul Mundt
2008-01-16  1:57       ` Paul Mundt

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=1198759779.6170.4.camel@localhost.localdomain \
    --to=adrian@newgolddream.dyndns.info \
    --cc=jens.axboe@oracle.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lkmladrian@gmail.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