public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-2.6-block:master 01/05] blk: implement generic dispatch queue
Date: Thu, 20 Oct 2005 12:00:03 +0200	[thread overview]
Message-ID: <20051020100003.GB2811@suse.de> (raw)
In-Reply-To: <20051019123429.1D0A2F29@htj.dyndns.org>

On Wed, Oct 19 2005, Tejun Heo wrote:
> @@ -40,6 +40,11 @@
>  static DEFINE_SPINLOCK(elv_list_lock);
>  static LIST_HEAD(elv_list);
>  
> +static inline sector_t rq_last_sector(struct request *rq)
> +{
> +	return rq->sector + rq->nr_sectors;
> +}

Slightly misnamed, since it's really the sector after the last sector
:-)

I've renamed that to rq_end_sector() instead.

> +/*
> + * Insert rq into dispatch queue of q.  Queue lock must be held on
> + * entry.  If sort != 0, rq is sort-inserted; otherwise, rq will be
> + * appended to the dispatch queue.  To be used by specific elevators.
> + */
> +void elv_dispatch_insert(request_queue_t *q, struct request *rq, int sort)
> +{
> +	sector_t boundary;
> +	unsigned max_back;
> +	struct list_head *entry;
> +
> +	if (!sort) {
> +		/* Specific elevator is performing sort.  Step away. */
> +		q->last_sector = rq_last_sector(rq);
> +		q->boundary_rq = rq;
> +		list_add_tail(&rq->queuelist, &q->queue_head);
> +		return;
> +	}
> +
> +	boundary = q->last_sector;
> +	max_back = q->max_back_kb * 2;
> +	boundary = boundary > max_back ? boundary - max_back : 0;

This looks really strange, what are you doing with boundary here?

> +	list_for_each_prev(entry, &q->queue_head) {
> +		struct request *pos = list_entry_rq(entry);
> +
> +		if (pos->flags & (REQ_SOFTBARRIER|REQ_HARDBARRIER|REQ_STARTED))
> +			break;
> +		if (rq->sector >= boundary) {
> +			if (pos->sector < boundary)
> +				continue;
> +		} else {
> +			if (pos->sector >= boundary)
> +				break;
> +		}
> +		if (rq->sector >= pos->sector)
> +			break;
> +	}
> +
> +	list_add(&rq->queuelist, entry);
> +}

I've split this into, I don't like rolled-up functions that really do
two seperate things. So elv_dispatch_sort() now does sorting,
elv_dispatch_add_tail() does what !sort would have done.

>  	while ((rq = __elv_next_request(q)) != NULL) {
> -		/*
> -		 * just mark as started even if we don't start it, a request
> -		 * that has been delayed should not be passed by new incoming
> -		 * requests
> -		 */
> -		rq->flags |= REQ_STARTED;
> +		if (!(rq->flags & REQ_STARTED)) {
> +			elevator_t *e = q->elevator;
> +
> +			/*
> +			 * This is the first time the device driver
> +			 * sees this request (possibly after
> +			 * requeueing).  Notify IO scheduler.
> +			 */
> +			if (blk_sorted_rq(rq) &&
> +			    e->ops->elevator_activate_req_fn)
> +				e->ops->elevator_activate_req_fn(q, rq);
> +
> +			/*
> +			 * just mark as started even if we don't start
> +			 * it, a request that has been delayed should
> +			 * not be passed by new incoming requests
> +			 */
> +			rq->flags |= REQ_STARTED;
> +		}
>  
>  		if (rq == q->last_merge)
>  			q->last_merge = NULL;
>  
> +		if (!q->boundary_rq || q->boundary_rq == rq) {
> +			q->last_sector = rq_last_sector(rq);
> +			q->boundary_rq = NULL;
> +		}

This seems to be the only place where you clear ->boundary_rq, that
can't be right. What about rq-to-rq merging, ->boundary_rq could be
freed and you wont notice. Generally I don't really like keeping
pointers to rqs around, it's given us problems in the past with the
last_merge bits even. For now I've added a clear of this in
__blk_put_request() as well.

>  int elv_queue_empty(request_queue_t *q)
>  {
>  	elevator_t *e = q->elevator;
>  
> +	if (!list_empty(&q->queue_head))
> +		return 0;
> +
>  	if (e->ops->elevator_queue_empty_fn)
>  		return e->ops->elevator_queue_empty_fn(q);
>  
> -	return list_empty(&q->queue_head);
> +	return 1;
>  }

Agree, this order definitely makes more sense.

> @@ -2475,14 +2478,14 @@ static void __blk_put_request(request_qu
>  
>  void blk_put_request(struct request *req)
>  {
> +	unsigned long flags;
> +	request_queue_t *q = req->q;
> +
>  	/*
> -	 * if req->rl isn't set, this request didnt originate from the
> -	 * block layer, so it's safe to just disregard it
> +	 * Gee, IDE calls in w/ NULL q.  Fix IDE and remove the
> +	 * following if (q) test.
>  	 */
> -	if (req->rl) {
> -		unsigned long flags;
> -		request_queue_t *q = req->q;
> -
> +	if (q) {

The q == NULL is because ide is using requests allocated on the stack,
I've wanted for that to die for many years :)

-- 
Jens Axboe


  reply	other threads:[~2005-10-20  9:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 12:35 [PATCH linux-2.6-block:master 00/05] blk: generic dispatch queue Tejun Heo
2005-10-19 12:35 ` [PATCH linux-2.6-block:master 01/05] blk: implement " Tejun Heo
2005-10-20 10:00   ` Jens Axboe [this message]
2005-10-20 13:45     ` Tejun Heo
2005-10-20 14:04       ` Jens Axboe
2005-10-20 14:19         ` Tejun Heo
2005-10-19 12:35 ` [PATCH linux-2.6-block:master 02/05] blk: update ioscheds to use " Tejun Heo
2005-10-20 11:21   ` Jens Axboe
2005-10-20 13:51     ` Tejun Heo
2005-10-20 14:11       ` Jens Axboe
2005-10-20 14:35         ` Tejun Heo
2005-10-20 14:41           ` Jens Axboe
2005-10-20 15:00             ` Tejun Heo
2005-10-20 17:07               ` Jens Axboe
2005-10-20 17:31                 ` Tejun Heo
2005-11-17 13:34               ` [PATCH linux-2.6-14-mm2] block: problem unloading I/O-Scheduler Module Dirk Henning Gerdes
2005-11-17 13:46                 ` Jens Axboe
2005-10-19 12:35 ` [PATCH linux-2.6-block:master 03/05] blk: move last_merge handling into generic elevator code Tejun Heo
2005-10-20 11:26   ` Jens Axboe
2005-10-19 12:35 ` [PATCH linux-2.6-block:master 04/05] blk: remove last_merge handling from ioscheds Tejun Heo
2005-10-20 11:26   ` Jens Axboe
2005-10-19 12:35 ` [PATCH linux-2.6-block:master 05/05] blk: update biodoc Tejun Heo
2005-10-20 11:27   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2005-07-26 13:56 [PATCH linux-2.6-block:master 00/05] blk: generic dispatch queue Tejun Heo
2005-07-26 13:56 ` [PATCH linux-2.6-block:master 01/05] blk: implement " Tejun Heo

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=20051020100003.GB2811@suse.de \
    --to=axboe@suse.de \
    --cc=htejun@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