All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
	Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH block-5.14] Revert "block/mq-deadline: Add cgroup support"
Date: Fri, 13 Aug 2021 11:43:30 -1000	[thread overview]
Message-ID: <YRbngn3f0eXtNi27@mtj.duckdns.org> (raw)
In-Reply-To: <5527319b-ba0c-00a3-19cf-612f2e2b073d@acm.org>

On Fri, Aug 13, 2021 at 10:17:42AM -0700, Bart Van Assche wrote:
> On 8/13/21 9:29 AM, Tejun Heo wrote:
> > The problem with complex optional hardware features is often the
> > accompanying variability in terms of availability, reliability and
> > behavior. The track record has been pretty sad. That isn't to say this
> > won't be useful for anybody but it'd need careful coordination in
> > terms of picking hardware vendor and model and ensuring vendor
> > support, which kinda severely limits the usefulness.
> 
> I think the above view is too negative. Companies that store large amounts
> of data have the power to make this happen by only buying storage devices
> that support I/O prioritization well enough.

The problem usually is that there always are other ways to skin that
cat which don't depend on having complex optional features. So, the
comparison isn't just about or among devices that support such extra
feature but with other solutions which don't need them in the first
place. Throw in the many inherent problems in expanding hardware
interface such as variability and timescale mismatch (hardware changes
a lot faster than software stack), the long term result tends to skew
pretty clearly.

Thanks.

-- 
tejun

  reply	other threads:[~2021-08-13 21:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 17:41 [PATCH block-5.14] Revert "block/mq-deadline: Add cgroup support" Tejun Heo
2021-08-11 18:49 ` Bart Van Assche
2021-08-11 19:14   ` Tejun Heo
2021-08-11 20:22     ` Bart Van Assche
2021-08-12 17:51       ` Tejun Heo
2021-08-12 18:16         ` Bart Van Assche
2021-08-12 19:23           ` Tejun Heo
2021-08-13  2:18             ` Damien Le Moal
2021-08-13 16:29               ` Tejun Heo
2021-08-13 17:17                 ` Bart Van Assche
2021-08-13 21:43                   ` Tejun Heo [this message]
2021-08-13 17:15               ` Bart Van Assche
2021-08-12 18:56         ` Jens Axboe
2021-08-12 19:10           ` Tejun Heo
2021-08-11 19:48 ` Jens Axboe
2021-08-12 14:14   ` Oleksandr Natalenko
2021-08-12 15:50     ` Jens Axboe

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=YRbngn3f0eXtNi27@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=Damien.LeMoal@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=linux-block@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.