From: Paul Bolle <pebolle@tiscali.nl>
To: "Matias Bjørling" <m@bjorling.me>
Cc: hch@infradead.org, axboe@fb.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
javier@paletta.io, keith.busch@intel.com
Subject: Re: [PATCH 2/5 v2] blk-mq: Support for Open-Channel SSDs
Date: Thu, 16 Apr 2015 11:10:08 +0200 [thread overview]
Message-ID: <1429175408.16771.45.camel@x220> (raw)
In-Reply-To: <1429101284-19490-3-git-send-email-m@bjorling.me>
A few things I spotted (while actually fiddling with 3/5).
On Wed, 2015-04-15 at 14:34 +0200, Matias Bjørling wrote:
> index f3dd028..58a8a71 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -221,6 +221,9 @@ static void blk_mq_rq_ctx_init(struct request_queue *q, struct blk_mq_ctx *ctx,
> rq->end_io = NULL;
> rq->end_io_data = NULL;
> rq->next_rq = NULL;
> +#if CONFIG_BLK_DEV_NVM
I think you meant
#ifdef CONFIG_BLK_DEV_NVM
> + rq->phys_sector = 0;
> +#endif
>
> ctx->rq_dispatched[rw_is_sync(rw_flags)]++;
> }
> --- /dev/null
> +++ b/block/blk-nvm.c
> +int nvm_register_target(struct nvm_target_type *tt)
> +{
> + int ret = 0;
> +
> + down_write(&_lock);
> + if (nvm_find_target_type(tt->name))
> + ret = -EEXIST;
> + else
> + list_add(&tt->list, &_targets);
> + up_write(&_lock);
> +
> + return ret;
> +}
> +
> +void nvm_unregister_target(struct nvm_target_type *tt)
> +{
> + if (!tt)
> + return;
> +
> + down_write(&_lock);
> + list_del(&tt->list);
> + up_write(&_lock);
> +}
Trying to build rrpc.ko I saw this
WARNING: "nvm_unregister_target" [[...]/drivers/lightnvm/rrpc.ko] undefined!
WARNING: "nvm_register_target" [[...]/drivers/lightnvm/rrpc.ko] undefined!
So I guess you need to export these two functions too.
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -209,6 +209,9 @@ struct request {
>
> /* for bidi */
> struct request *next_rq;
> +#if CONFIG_BLK_DEV_NVM
Again, I think
#ifdef CONFIG_BLK_DEV_NVM
> + sector_t phys_sector;
> +#endif
> };
>
> static inline unsigned short req_get_ioprio(struct request *req)
Paul Bolle
next prev parent reply other threads:[~2015-04-16 9:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 12:34 [PATCH 0/5 v2] Support for Open-Channel SSDs Matias Bjørling
2015-04-15 12:34 ` [PATCH 1/5 v2] blk-mq: Add prep/unprep support Matias Bjørling
2015-04-17 6:34 ` Christoph Hellwig
2015-04-17 8:15 ` Matias Bjørling
2015-04-17 17:46 ` Christoph Hellwig
2015-04-18 6:45 ` Matias Bjorling
2015-04-18 20:16 ` Christoph Hellwig
2015-04-19 18:12 ` Matias Bjorling
2015-04-15 12:34 ` [PATCH 2/5 v2] blk-mq: Support for Open-Channel SSDs Matias Bjørling
2015-04-16 9:10 ` Paul Bolle [this message]
2015-04-16 10:23 ` Matias Bjørling
2015-04-16 11:34 ` Paul Bolle
2015-04-16 13:29 ` Matias Bjørling
2015-04-15 12:34 ` [PATCH 3/5 v2] lightnvm: RRPC target Matias Bjørling
2015-04-16 9:12 ` Paul Bolle
2015-04-15 12:34 ` [PATCH 4/5 v2] null_blk: LightNVM support Matias Bjørling
2015-04-15 12:34 ` [PATCH 5/5 v2] nvme: " Matias Bjørling
2015-04-16 14:55 ` Keith Busch
2015-04-16 15:14 ` Javier González
2015-04-16 15:52 ` Keith Busch
2015-04-16 16:01 ` James R. Bergsten
2015-04-16 16:12 ` Keith Busch
2015-04-16 17:17 ` Matias Bjorling
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=1429175408.16771.45.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=javier@paletta.io \
--cc=keith.busch@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=m@bjorling.me \
/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).