linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: jens.axboe@oracle.com
Cc: fujita.tomonori@lab.ntt.co.jp, bzolnier@gmail.com,
	linux-scsi@vger.kernel.org, bharrosh@panasas.com,
	linux-ide@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 4/4] block: add large command support
Date: Thu, 17 Apr 2008 13:02:00 +0900	[thread overview]
Message-ID: <20080417125900E.tomof@acm.org> (raw)
In-Reply-To: <20080416083305.GY12774@kernel.dk>

On Wed, 16 Apr 2008 10:33:06 +0200
Jens Axboe <jens.axboe@oracle.com> wrote:

> On Wed, Apr 16 2008, FUJITA Tomonori wrote:
> > On Wed, 16 Apr 2008 00:50:54 +0200
> > Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> > 
> > > 
> > > Hi,
> > > 
> > > On Monday 14 April 2008, Jens Axboe wrote:
> > > > On Mon, Apr 14 2008, FUJITA Tomonori wrote:
> > > > > This patch changes rq->cmd from the static array to a pointer to
> > > > > support large commands.
> > > > > 
> > > > > We rarely handle large commands. So for optimization, a struct request
> > > > > still has a static array for a command. rq_init sets rq->cmd pointer
> > > > > to the static array.
> > > > > 
> > > > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > > > > Cc: Jens Axboe <jens.axboe@oracle.com>
> > > > > ---
> > > > >  block/blk-core.c       |    1 +
> > > > >  drivers/ide/ide-io.c   |    1 +
> > > > >  include/linux/blkdev.h |   12 ++++++++++--
> > > > >  3 files changed, 12 insertions(+), 2 deletions(-)
> > > > > 
> > > > > diff --git a/block/blk-core.c b/block/blk-core.c
> > > > > index 6669238..6f0968f 100644
> > > > > --- a/block/blk-core.c
> > > > > +++ b/block/blk-core.c
> > > > > @@ -132,6 +132,7 @@ void rq_init(struct request_queue *q, struct request *rq)
> > > > >  	rq->errors = 0;
> > > > >  	rq->ref_count = 1;
> > > > >  	rq->cmd_len = 0;
> > > > > +	rq->cmd = rq->__cmd;
> > > > >  	memset(rq->cmd, 0, BLK_MAX_CDB);
> > > > >  	rq->data_len = 0;
> > > > >  	rq->extra_len = 0;
> > > > > diff --git a/drivers/ide/ide-io.c b/drivers/ide/ide-io.c
> > > > > index 7153796..bac5ea1 100644
> > > > > --- a/drivers/ide/ide-io.c
> > > > > +++ b/drivers/ide/ide-io.c
> > > > > @@ -1595,6 +1595,7 @@ void ide_init_drive_cmd (struct request *rq)
> > > > >  {
> > > > >  	memset(rq, 0, sizeof(*rq));
> > > > >  	rq->ref_count = 1;
> > > > > +	rq->cmd = rq->__cmd;
> > > > >  }
> > > 
> > > Tomo, some more changes are needed:
> > > 
> > > Please think about all _static_/dynamic allocations of 'struct request'
> > > used together with REQ_TYPE_SPECIAL etc., i.e.
> > 
> > I think that using struct request allocated statically is wrong from
> > the perspective of the block layer design, that is, you always need to
> > use blk_get_request. I think that except ide, everyone does.
> > 
> > I try to convert ide to use blk_get_request properly if you want.
> 
> That would be best, but the on-stack allocation has the benefit that
> it'll always work. So until we can completely get rid of that, lets just
> make it a hard rule that ANY rq allocation MUST call rq_init(). It's a
> lot saner than doing a memset() anyway.

I'm fine with that.

There is one minor issue. rq_init doesn't initialize rq->cmd_flags so
the callers need to do it for themselves (If they don't, probably they
hit BUG_ON in blk_queue_end_tag).

  parent reply	other threads:[~2008-04-17  4:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080414010112W.tomof@acm.org>
     [not found] ` <1208170266-1676-1-git-send-email-fujita.tomonori@lab.ntt.co.jp>
     [not found]   ` <1208170266-1676-2-git-send-email-fujita.tomonori@lab.ntt.co.jp>
     [not found]     ` <1208170266-1676-3-git-send-email-fujita.tomonori@lab.ntt.co.jp>
2008-04-14 10:50       ` [PATCH 3/4] block: replace sizeof(rq->cmd) with BLK_MAX_CDB FUJITA Tomonori
2008-04-14 10:50         ` [PATCH 4/4] block: add large command support FUJITA Tomonori
2008-04-14 11:29           ` Jens Axboe
2008-04-14 12:08             ` FUJITA Tomonori
2008-04-15 22:50             ` Bartlomiej Zolnierkiewicz
2008-04-15 22:57               ` FUJITA Tomonori
2008-04-16  0:22                 ` Bartlomiej Zolnierkiewicz
2008-04-16  8:33                 ` Jens Axboe
2008-04-16  9:08                   ` Boaz Harrosh
2008-04-16  9:42                     ` Jens Axboe
2008-04-16 22:28                       ` Bartlomiej Zolnierkiewicz
2008-04-17  3:59                     ` FUJITA Tomonori
2008-04-17  7:07                       ` Jens Axboe
2008-04-17 11:55                         ` Bartlomiej Zolnierkiewicz
2008-04-17 11:58                           ` Bartlomiej Zolnierkiewicz
2008-04-17 12:07                         ` FUJITA Tomonori
2008-04-17  4:02                   ` FUJITA Tomonori [this message]
2008-04-14 14:41           ` Pete Wyckoff
2008-04-14 22:33             ` FUJITA Tomonori
2008-04-15 13:44               ` Pete Wyckoff
2008-04-15  7:45             ` Boaz Harrosh
2008-04-15 10:05               ` FUJITA Tomonori
2008-04-15  7:29           ` Jens Axboe

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=20080417125900E.tomof@acm.org \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=bharrosh@panasas.com \
    --cc=bzolnier@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).