From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: bharrosh@panasas.com, bzolnier@gmail.com,
James.Bottomley@HansenPartnership.com, pw@osc.edu,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [RFC 0/5] block large commands support continue
Date: Fri, 25 Apr 2008 12:25:56 +0200 [thread overview]
Message-ID: <20080425102555.GL12774@kernel.dk> (raw)
In-Reply-To: <20080425190349I.tomof@acm.org>
On Fri, Apr 25 2008, FUJITA Tomonori wrote:
> On Fri, 25 Apr 2008 11:31:41 +0200
> Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > On Fri, Apr 25 2008, FUJITA Tomonori wrote:
> > > On Fri, 25 Apr 2008 11:22:04 +0200
> > > Jens Axboe <jens.axboe@oracle.com> wrote:
> > >
> > > > On Fri, Apr 25 2008, FUJITA Tomonori wrote:
> > > > > On Thu, 24 Apr 2008 12:49:30 +0200
> > > > > Jens Axboe <jens.axboe@oracle.com> wrote:
> > > > >
> > > > > > On Thu, Apr 24 2008, FUJITA Tomonori wrote:
> > > > > > > On Thu, 24 Apr 2008 13:31:21 +0900
> > > > > > > FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> > > > > > >
> > > > > > > > On Wed, 23 Apr 2008 17:50:42 +0300
> > > > > > > > Boaz Harrosh <bharrosh@panasas.com> wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > > The support for large commands was dropped from the for-2.6.26 branch
> > > > > > > > > and will probably not get accepted into next kernel.
> > > > > > > > >
> > > > > > > > > I have tried to take all comments from Jens and Bart. and incorporate
> > > > > > > > > it into a new patchset. This is basically Tomo's patchset but with
> > > > > > > > > proposed changes.
> > > > > > > >
> > > > > > > > Have you seen the patchset to remove request on the stack?
> > > > > > > >
> > > > > > > > http://marc.info/?l=linux-ide&m=120882410712466&w=2
> > > > > > > >
> > > > > > > >
> > > > > > > > > They are based on current linux-block/master. They will probably conflict with
> > > > > > > > > latest patch sent by Tomo for the blk_get_request(). Once those patches
> > > > > > > > > get accepted at some git tree, (Where will that be?), I will rebase these
> > > > > > > > > on top of them. Please CC me of any progress.
> > > > > > > > >
> > > > > > > > > [PATCH 1/5] block: no need to initialize rq->cmd
> > > > > > > > > This is 2 of Tomo's patches squashed together as they are
> > > > > > > > > small and do the same. Tomo is this OK?
> > > > > > > > >
> > > > > > > > > [PATCH 2/5] block: replace sizeof(rq->cmd) with BLK_MAX_CDB
> > > > > > > > > Tomos patch rebased to here
> > > > > > > > >
> > > > > > > > > [PATCH 3/5] block: Export rq_init, rename to blk_init_rq
> > > > > > > > > [PATCH 4/5] block: Use new blk_init_rq
> > > > > > > > > These patches are basically what Jens and Bart has suggested, that with
> > > > > > > > > a small code change to blk-core.c we can memset at rq_init() and only set
> > > > > > > > > none zero members. We can also export that initializer and use it all over
> > > > > > > > > the ide tree where ever requests don't come from a request queue. (OK also
> > > > > > > > > at scsi_error.c)
> > > > > > > >
> > > > > > > > +void blk_init_rq(struct request_queue *q, struct request *rq, int cmd_flags)
> > > > > > > >
> > > > > > > > Hmm, would it be better to modify the block layer to let rq_init just
> > > > > > > > memset() the request structure?
> > > > > > >
> > > > > > > I think, if we move rq_init to blk_alloc_request from get_request,
> > > > > > > rq_init can just memset() the structure.
> > > > > > >
> > > > > > > Then we can export rq_init and rq_init works for everyone.
> > > > > >
> > > > > > Wont work, see the io scheduler set_request() functions.
> > > > >
> > > > > Sorry, can you be more specific?
> > > > >
> > > > > Only cfq uses set_request for now. cfq_set_request uses rq->cmd_flags
> > > > > and stores information at rq->elevator_private and
> > > > > rq->elevator_private2.
> > > > >
> > > > > The patch does memset() the request structure and sets up
> > > > > rq->cmd_flags, and then elv_set_request. Doesn't it work?
> > > >
> > > > Sorry, with the moved rq_init() it should work, didn't look closely
> > > > enough.
> > >
> > > No problem.
> > >
> > > So are you ok with the patch? If so, I'll re-send it with a proper
> > > description and the signed-off.
> >
> > Please do - I actually already merged it, but do resend with a full
> > description and signed-off etc.
>
> I just stole your description and added my signed-off.
OK, will update it.
> Will you merge the large command support for 2.6.26? Or only this
> clean-up patch?
It's both, we can merge large command support for 2.6.26.
--
Jens Axboe
next prev parent reply other threads:[~2008-04-25 10:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 14:50 [RFC 0/5] block large commands support continue Boaz Harrosh
2008-04-23 14:57 ` [PATCH 1/5] block: no need to initialize rq->cmd Boaz Harrosh
2008-04-23 15:28 ` Boaz Harrosh
2008-04-23 15:01 ` [PATCH 2/5] block: replace sizeof(rq->cmd) with BLK_MAX_CDB Boaz Harrosh
2008-04-23 15:05 ` [RFC PATCH 3/5] block: Export rq_init, rename to blk_init_rq Boaz Harrosh
2008-04-23 15:09 ` [RFC PATCH 4/5] block: Use new blk_init_rq Boaz Harrosh
2008-04-23 15:13 ` [PATCH 5/5] block: add large command support Boaz Harrosh
2008-04-24 4:31 ` [RFC 0/5] block large commands support continue FUJITA Tomonori
2008-04-24 6:19 ` FUJITA Tomonori
2008-04-24 10:49 ` Jens Axboe
2008-04-24 15:17 ` FUJITA Tomonori
2008-04-25 9:22 ` Jens Axboe
2008-04-25 9:27 ` FUJITA Tomonori
2008-04-25 9:31 ` Jens Axboe
2008-04-25 10:03 ` FUJITA Tomonori
2008-04-25 10:25 ` Jens Axboe [this message]
2008-04-25 10:29 ` FUJITA Tomonori
2008-04-27 8:26 ` Boaz Harrosh
2008-04-27 8:42 ` FUJITA Tomonori
2008-04-27 8:42 ` FUJITA Tomonori
2008-04-27 9:06 ` 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=20080425102555.GL12774@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=bzolnier@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pw@osc.edu \
/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).