All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	hch@infradead.org, axboe@fb.com, dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UBI: Block: Add blk-mq support
Date: Sun, 02 Nov 2014 23:49:28 +0100	[thread overview]
Message-ID: <5456B4F8.1000608@nod.at> (raw)
In-Reply-To: <5456AFEA.6000507@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

Am 02.11.2014 um 23:27 schrieb Ezequiel Garcia:
> Wow. Where did you run this and on top of what storage device?

nandsim, to make sure that the MTD is not our bottleneck.

> I'm still interested in the memory footprint, UBI is already heavy enough.

AFAICT blk-mq allocates one struct ubiblock_pdu per device.
As all IO is done via scattergather the memory footprint should be good.
But I'm sure Christoph can tell you the glory details.

>>> I kind of like the negative diffstat, but the code doesn't look cleaner
>>> or simpler.
>>>
>>> In other words, we need a good reason before we agree on making this
>>> "zen style" driver more complex.
>>
>> After reading my patch again I think we could move ubiblock_read_to_sg()
>> to kapi.c or io.c. It is rather generic and maybe we can tun more UBI users to
>> scattergather such that less vmalloc()s are needed.
>>
>> This would also make the diffstat nicer...
>>
> 
> Yes, any additional effort to make the current patch any simpler would
> be great. In its current form it seems rather cumbersome to me.

Why cumbersome? It changes the way the driver works as blk-mq works differently.
If you look at other blk-mq conversion patches you'll notice that they all change
a lot.

> If you can re-submit something better and put a more verbose commit log,
> I'd really appreciate it :)

First I wait for a review. I'm not sure whether I'm used blk-ml correctly.

Thanks,
//richard



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	hch@infradead.org, axboe@fb.com, dedekind1@gmail.com
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UBI: Block: Add blk-mq support
Date: Sun, 02 Nov 2014 23:49:28 +0100	[thread overview]
Message-ID: <5456B4F8.1000608@nod.at> (raw)
In-Reply-To: <5456AFEA.6000507@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

Am 02.11.2014 um 23:27 schrieb Ezequiel Garcia:
> Wow. Where did you run this and on top of what storage device?

nandsim, to make sure that the MTD is not our bottleneck.

> I'm still interested in the memory footprint, UBI is already heavy enough.

AFAICT blk-mq allocates one struct ubiblock_pdu per device.
As all IO is done via scattergather the memory footprint should be good.
But I'm sure Christoph can tell you the glory details.

>>> I kind of like the negative diffstat, but the code doesn't look cleaner
>>> or simpler.
>>>
>>> In other words, we need a good reason before we agree on making this
>>> "zen style" driver more complex.
>>
>> After reading my patch again I think we could move ubiblock_read_to_sg()
>> to kapi.c or io.c. It is rather generic and maybe we can tun more UBI users to
>> scattergather such that less vmalloc()s are needed.
>>
>> This would also make the diffstat nicer...
>>
> 
> Yes, any additional effort to make the current patch any simpler would
> be great. In its current form it seems rather cumbersome to me.

Why cumbersome? It changes the way the driver works as blk-mq works differently.
If you look at other blk-mq conversion patches you'll notice that they all change
a lot.

> If you can re-submit something better and put a more verbose commit log,
> I'd really appreciate it :)

First I wait for a review. I'm not sure whether I'm used blk-ml correctly.

Thanks,
//richard



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-11-02 22:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02 13:00 [PATCH] UBI: Block: Add blk-mq support Richard Weinberger
2014-11-02 13:00 ` Richard Weinberger
2014-11-02 21:52 ` Ezequiel Garcia
2014-11-02 21:52   ` Ezequiel Garcia
2014-11-02 22:21   ` Richard Weinberger
2014-11-02 22:21     ` Richard Weinberger
2014-11-02 22:27     ` Ezequiel Garcia
2014-11-02 22:27       ` Ezequiel Garcia
2014-11-02 22:49       ` Richard Weinberger [this message]
2014-11-02 22:49         ` Richard Weinberger
2014-11-03  1:20         ` Jens Axboe
2014-11-03  1:20           ` Jens Axboe
2014-11-03  1:18   ` Jens Axboe
2014-11-03  1:18     ` Jens Axboe
2014-11-03  5:03 ` Ming Lei
2014-11-03  5:03   ` Ming Lei
2014-11-03 13:58   ` Ezequiel Garcia
2014-11-03 13:58     ` Ezequiel Garcia
2014-11-03 18:22     ` Richard Weinberger
2014-11-03 18:22       ` Richard Weinberger
2014-11-03  8:18 ` Christoph Hellwig
2014-11-03  8:18   ` Christoph Hellwig
2014-11-03  8:23   ` Richard Weinberger
2014-11-03  8:23     ` Richard Weinberger
2014-11-07  9:46     ` Artem Bityutskiy
2014-11-07  9:46       ` Artem Bityutskiy
2014-11-07  9:53       ` Richard Weinberger
2014-11-07  9:53         ` Richard Weinberger
2014-11-07  9:56         ` Artem Bityutskiy
2014-11-07  9:56           ` Artem Bityutskiy

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=5456B4F8.1000608@nod.at \
    --to=richard@nod.at \
    --cc=axboe@fb.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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.