From: Boaz Harrosh <bharrosh@panasas.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jens Axboe <jens.axboe@oracle.com>,
Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
open-osd mailing-list <osd-dev@open-osd.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH version2] bsg: Add support for submitting requests at tail of queue
Date: Sun, 25 Jan 2009 11:44:21 +0200 [thread overview]
Message-ID: <497C3475.1060907@panasas.com> (raw)
In-Reply-To: <497C33D8.1060802@panasas.com>
Boaz Harrosh wrote:
> Currently inherited from sg.c bsg will submit asynchronous request
> at the head-of-the-queue, (using "at_head" set in the call to
> blk_execute_rq_nowait()). This is bad in situation where the queues
> are full but requests need to execute in order. Failing to do that can
> cause the first submitted commands to never execute.
>
> The sg_io_v4->flags member is used and a bit is allocated to denote the
> Q_AT_TAIL. Zero is to queue at_head as before, to be compatible with old
> code at the write/read path. SG_IO code path behavior was changed so to
> be the same as write/read behavior. SG_IO was very rarely used and breaking
> compatibility with it is OK at this stage.
>
> sg_io_hdr at sg.h also has a flags member and uses 3 bits from the first
> nibble and one bit from the last nibble. Even though none of these bits
> are supported by bsg, The second nibble is allocated for use by bsg. Just
> in case.
>
> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
> CC: Douglas Gilbert <dgilbert@interlog.com>
> ---
> block/bsg.c | 9 +++++++--
> include/linux/bsg.h | 8 ++++++++
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
Sorrrrrrry bad patch, teach me to never send a patch in the morning
before coffee.
Will send a version 3
Boaz
next prev parent reply other threads:[~2009-01-25 9:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 9:52 [PATCH] bsg: Add support for submitting requests at tail of queue Boaz Harrosh
2009-01-21 23:24 ` FUJITA Tomonori
2009-01-22 8:57 ` Boaz Harrosh
2009-01-22 11:13 ` Jens Axboe
2009-01-22 12:44 ` Boaz Harrosh
2009-01-22 12:46 ` Jens Axboe
2009-01-22 22:03 ` FUJITA Tomonori
2009-01-22 22:27 ` James Bottomley
2009-01-23 6:14 ` FUJITA Tomonori
2009-01-25 9:17 ` Boaz Harrosh
2009-01-25 9:41 ` [PATCH version2] " Boaz Harrosh
2009-01-25 9:44 ` Boaz Harrosh [this message]
2009-01-25 10:07 ` [PATCH version 3] " Boaz Harrosh
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=497C3475.1060907@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dougg@torque.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=osd-dev@open-osd.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