mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] first round of SCSI updates for the 6.4+ merge window
Date: Sun, 03 Sep 2023 08:41:41 +0100	[thread overview]
Message-ID: <2740c0e76e3feffbd43956d342c1805082396c99.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=wgA6CBwnJ02H+vSgneKPcPRP0BWQ-Kx2Re1B56Y2hXkFQ@mail.gmail.com>

On Sat, 2023-09-02 at 12:08 -0700, Linus Torvalds wrote:
> On Sat, 2 Sept 2023 at 00:39, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > 
> > Updates to the usual drivers (ufs, lpfc, qla2xxx, mpi3mr, libsas)
> > and the usual minor updates and bug fixes but no significant core
> > changes.
> 
> Removing 3000+ lines for UFS HPB support wasn't even worth
> mentioning?

Sorry, my bias is showing.  I always thought HPB was a useless
marketing feature and was against including it, so removing it is just
the world going back to being more correct.  To be honest, I also
didn't think you cared at all about UFS ...

> I am happy to see it gone, and maybe as a technology it was a failure
> not worth it, but as a "we gave up on it as being worthless" might
> still have been worth a word or two..
> 
> Sadly, I see from the commit message that apparently the next stage
> is going to involve zoned storage. Now *there* is a technology that
> seems to be a complete failure, brought to us by the same kind of
> failed hardware people who tried to convince us that we should care
> about 64kB pages in SSD's.

Well, we put HPB in in spite of most of us thinking it was a bad idea
because there was a tiny chance it might work and it could be yanked
out if it didn't.  There's no reason not to extend the same courtesy to
zoned storage.

> Oh well. With enough thrust, even a pig will fly. I suspect that's
> the motivating factor behind all those zoned storage things too.

That's why RFC1925 exists, yes ...

James


  reply	other threads:[~2023-09-03  7:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-02  7:39 James Bottomley
2023-09-02 19:08 ` Linus Torvalds
2023-09-03  7:41   ` James Bottomley [this message]
2023-09-02 19:18 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02 12:28 James Bottomley
2023-11-03  1:26 ` pr-tracker-bot
2023-06-29 12:48 James Bottomley
2023-06-30 19:14 ` Linus Torvalds
2023-07-03 17:09   ` Mike Christie
2023-07-03 17:25     ` Linus Torvalds
2023-06-30 19:28 ` pr-tracker-bot

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=2740c0e76e3feffbd43956d342c1805082396c99.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®