From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Aravamudan Date: Tue, 15 Feb 2005 01:43:49 +0000 Subject: [KJ] Re: [PATCH] 18/34: ieee1394/video1394: replace Message-Id: <20050215014349.GA12794@us.ibm.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============34097601145684342==" List-Id: References: <20050215002049.GH9231@conscoop.ottawa.on.ca> In-Reply-To: <20050215002049.GH9231@conscoop.ottawa.on.ca> To: kernel-janitors@vger.kernel.org --===============34097601145684342== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 14, 2005 at 08:34:20PM -0500, Jody McIntyre wrote: > On Mon, Feb 14, 2005 at 04:50:47PM -0800, Nishanth Aravamudan wrote: > > > > In my copy, it _unlocks_ around the sleep. I don't see why this > > > couldn't be done with wait_event_interruptible (unlock, wait, lock). > > > Can you produce a patch with that? I'll find a video1394 user to test > > > it. > > > > Sorry for my mis-statement/lack of clarity. In my copy, it also unlocks > > around the sleep... The problem is that wait_event*() should be used in > > such a way that the while-loop is not at all necessary (ideally). > > Instead, we'll have a while-loop around the unlock-wait_event-lock code, > > which is just ugly to me, as wait_event is just a macro around another > > while loop. The real solution is wait_event_interruptible_lock(). > > Hopefully I can get such a macro accepted into mainline sooner or > > later... > > So you want to leave tho old code in until then? Fair enough. Yup, I think that's the best solution for now. > > I'm assuming the locking is done this way so that other variables protected by > > the same lock can be changed while this one sleeps? > > Correct. See, for example, wakeup_dma_ir_ctx() . That's what I thought, but I just wanted to get confirmation from you :) Thanks for all the feedback! I will send an updated patch against the bk-repo once the other wait_event*() macros go in (expect it before 2.6.12's full release). Thanks, Nish --===============34097601145684342== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline _______________________________________________ Kernel-janitors mailing list Kernel-janitors@lists.osdl.org http://lists.osdl.org/mailman/listinfo/kernel-janitors --===============34097601145684342==--