public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: cable_plug <pratapagiri.ak@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: problem with ending requests asynchronously in my block device driver
Date: Mon, 17 Dec 2007 12:21:03 -0800 (PST)	[thread overview]
Message-ID: <14374028.post@talk.nabble.com> (raw)


Hi, 

I've a block device driver which does the following, 

Inside the request function I do something like this: 
request(fn) { 

 while ((req = elv_next_request(q)) != NULL) { 
....................set up the request; 
 spin_unlock_irq(q->queue_lock); 
call the transfer(set_up_req) function; 
spin_lock_irq(q->queue_lock); 
} 
       spin_unlock_irq (q->queue_lock); 
        /* allow callback to execute as it needs the lock!!! */ 
        spin_lock_irq (q->queue_lock); 


} 
and the transfer function calls the scsi_execute_asyn(....) with the
callback function doing the end request. So, the ending of the request is
done like below: 

callback(fn) { 

 spin_lock_irqsave(q->queue_lock, flags); 
        if (!end_that_request_first(set_up_req->req, cmpstatus, 
                        set_up_req->req->nr_sectors)) { 
                add_disk_randomness(...); 
                end_that_request_last(set_up_req->req,0); 
        } 
        spin_unlock_irqrestore(q->queue_lock, flags); 
} 


This code works fine with most of the kernel versions, but fails on some
like , Linux 2.6.18-8.el5-xen 

Please help me to find out where I'm going wrong? 

when I say 'fails' it just hangs without any error ....I'm using dt(Data
test) to write to the disk. The logs show that all the requests that have
been sent for processing, have completed sucessfully. Its just that new
requests never enter the request function. So, the dt writes almost half the
data and then simply hangs. 

  
  The actual code does nothing but, call the scsi_execute_async , which 
 later on calls the callback function which is used to end the request. 
 So, both the callback function and the request function need to share 
 the queue lock. So the code samples I sent cover all the aspects of my 
 program. What I'm looking for here is how can I end the requests 
 asynchronously much later after the request processing is done. Please note 
 here that the asynchronous end requests is done by the callback function 
 of the scsi_execute_async, which needs to share the queue lock with 
 the request function. 
    
  when I say 'fails' it just hangs without any error ....I'm using 
 dt(Data 
test) to write to the disk. The logs show that all the requests that 
 have 
been sent for processing, have completed successfully. Its just that new 
requests never enter the request function. So, the dt writes almost 
 half the 
data and then simply hangs. 


Thanks in advance for an early reply. 
Anil P.
-- 
View this message in context: http://www.nabble.com/problem-with-ending-requests-asynchronously-in-my-block-device-driver-tp14374028p14374028.html
Sent from the linux-kernel mailing list archive at Nabble.com.


             reply	other threads:[~2007-12-17 20:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 20:21 cable_plug [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-17 19:50 problem with ending requests asynchronously in my block device driver cable_plug
2007-12-17 15:52 a_kumar
2007-12-15 21:57 a_kumar
2007-12-15 21:07 a_kumar
2007-12-15 20:52 a_kumar
2007-12-16  9:23 ` Jon Masters

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=14374028.post@talk.nabble.com \
    --to=pratapagiri.ak@gmail.com \
    --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