From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] add bsg queue resize
Date: Wed, 24 Jan 2007 09:04:57 +0100 [thread overview]
Message-ID: <20070124080456.GB12718@kernel.dk> (raw)
In-Reply-To: <20070124111613M.fujita.tomonori@lab.ntt.co.jp>
On Wed, Jan 24 2007, FUJITA Tomonori wrote:
> From: Jens Axboe <jens.axboe@oracle.com>
> Subject: Re: [PATCH] add bsg queue resize
> Date: Tue, 23 Jan 2007 16:23:49 +0100
>
> > On Tue, Jan 23 2007, Jens Axboe wrote:
> > > On Sat, Jan 20 2007, FUJITA Tomonori wrote:
> > > > This enables bsg to resize the queue depth via
> > > > SG_SET_COMMAND_Q. bsg_command structures are allocated via mempool
> > > > because the previous way to use contiguous memory makes it difficult
> > > > to resize the queue depth when a bsg_device has outstanding commands.
> > >
> > > Overall the patch looks fine. I don't think we need a mempool though,
> > > and allocations could just use GFP_USER from the user invoked queuing
> > > paths. Just make it GFP_USER, we can always extend the
> > > bsg_alloc_command() to take a gfp_t argument as well If you get rid of
> > > the mempool, then resizing is simply just adjusting bd->max_queue.
> >
> > Like so.
>
> Thanks. I thought that pre-allocating bsg_command structures would be
> nice. But it doesn't matter much for me.
Probably not very useful in the end, we need to allocate some other
structures for IO anyway.
> One minor comment is that we could simplify __bsg_alloc_command
> failpath a bit?
Yep, applied. Another thing that needs cleaning up for the allocation is
the whole bsg_io_schedule() stuff.
--
Jens Axboe
prev parent reply other threads:[~2007-01-24 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 14:25 [PATCH] add bsg queue resize FUJITA Tomonori
2007-01-21 4:09 ` Jens Axboe
2007-01-23 8:34 ` Jens Axboe
2007-01-23 15:23 ` Jens Axboe
2007-01-24 2:25 ` FUJITA Tomonori
2007-01-24 8:04 ` Jens Axboe [this message]
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=20070124080456.GB12718@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.