From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [patch 5/5] block: use a driver-specific handler for the "inflight" value
Date: Wed, 14 Nov 2018 07:18:48 -0800 [thread overview]
Message-ID: <20181114151848.GA22138@infradead.org> (raw)
In-Reply-To: <20181108170701.GA29107@redhat.com>
On Thu, Nov 08, 2018 at 12:07:01PM -0500, Mike Snitzer wrote:
> Discussed doing that with Jens and reported as much here:
>
> https://www.redhat.com/archives/dm-devel/2018-November/msg00068.html
>
> And Jens gave additional context for why yet another attempt to switch
> block core's in_flight to percpu counters is doomed (having already been
> proposed and rejected twice):
>
> https://www.redhat.com/archives/dm-devel/2018-November/msg00071.html
>
> And yes, definitely should've cc'd linux-block (now added).
So how is dm different from the the other 3 handful of drivers using
the make_request interface that the per-cpu counters work for dm and
not the others?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Mikulas Patocka <mpatocka@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
axboe@kernel.dk
Subject: Re: [patch 5/5] block: use a driver-specific handler for the "inflight" value
Date: Wed, 14 Nov 2018 07:18:48 -0800 [thread overview]
Message-ID: <20181114151848.GA22138@infradead.org> (raw)
In-Reply-To: <20181108170701.GA29107@redhat.com>
On Thu, Nov 08, 2018 at 12:07:01PM -0500, Mike Snitzer wrote:
> Discussed doing that with Jens and reported as much here:
>
> https://www.redhat.com/archives/dm-devel/2018-November/msg00068.html
>
> And Jens gave additional context for why yet another attempt to switch
> block core's in_flight to percpu counters is doomed (having already been
> proposed and rejected twice):
>
> https://www.redhat.com/archives/dm-devel/2018-November/msg00071.html
>
> And yes, definitely should've cc'd linux-block (now added).
So how is dm different from the the other 3 handful of drivers using
the make_request interface that the per-cpu counters work for dm and
not the others?
next prev parent reply other threads:[~2018-11-14 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:35 [patch 5/5] block: use a driver-specific handler for the "inflight" value Mikulas Patocka
2018-11-08 14:52 ` Christoph Hellwig
2018-11-08 17:07 ` Mike Snitzer
2018-11-08 17:07 ` Mike Snitzer
2018-11-14 15:18 ` Christoph Hellwig [this message]
2018-11-14 15:18 ` Christoph Hellwig
2018-11-14 15:34 ` Mike Snitzer
2018-11-14 15:34 ` Mike Snitzer
2018-11-14 22:49 ` Mikulas Patocka
2018-11-14 22:49 ` Mikulas Patocka
2018-11-14 22:35 ` Mikulas Patocka
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=20181114151848.GA22138@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@redhat.com \
/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.