From: Tim Walker <tim.t.walker@seagate.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Muhammad Ahmad <muhammad.ahmad@seagate.com>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] Multi-actuator HDDs
Date: Tue, 11 Feb 2020 14:23:03 -0500 [thread overview]
Message-ID: <CANo=J14NY9TG9RAUMfX2N-q2ZCqiD0CGGVWu-DTgKJDQK20CRg@mail.gmail.com> (raw)
In-Reply-To: <20200210215222.GB10776@dread.disaster.area>
On Mon, Feb 10, 2020 at 4:52 PM Dave Chinner <david@fromorbit.com> wrote:
>
> On Mon, Feb 10, 2020 at 12:01:13PM -0600, Muhammad Ahmad wrote:
> > Background:
> > As the capacity of HDDs increases so is the need to increase
> > performance to efficiently utilize this increase in capacity. The
> > current school of thought is to use Multi-Actuators to increase
> > spinning disk performance. Seagate has already announced it’s SAS
> > Dual-Lun, Dual-Actuator device. [1]
> >
> > Discussion Proposal:
> > What impacts multi-actuator HDDs has on the linux storage stack?
> >
> > A discussion on the pros & cons of accessing the actuators through a
> > single combined LUN or multiple individual LUNs? In the single LUN
> > scenario, how should the device communicate it’s LBA to actuator
> > mapping? In the case of multi-lun, how should we manage commands that
> > affect both actuators?
>
> What ground does this cover that wasn't discussed a couple of years
> ago at LSFMM?
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lwn.net_Articles_753652_&d=DwIDaQ&c=IGDlg0lD0b-nebmJJ0Kp8A&r=NW1X0yRHNNEluZ8sOGXBxCbQJZPWcIkPT0Uy3ynVsFU&m=2Eb6xxsYMqNOn4F3Yiola3ef2BTCKKg06zpnqJ_m1c8&s=JtxAw3Y13PHlYJygS847dBUVRXeM061Snm3hq01DFlY&e=
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
Hi all-
The multi-actuator fundamentals remain the same from a couple of years
ago. One development is to combine the actuators' address spaces into
a single LUN. We'd like to show you a couple of system block diagrams,
and talk about the queue management and command scheduling.
Best regards,
-Tim
--
Tim Walker
Product Design Systems Engineering, Seagate Technology
(303) 775-3770
next prev parent reply other threads:[~2020-02-11 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 18:01 [LSF/MM/BPF TOPIC] Multi-actuator HDDs Muhammad Ahmad
2020-02-10 18:26 ` Keith Busch
2020-02-11 19:18 ` James Bottomley
2020-02-10 21:52 ` Dave Chinner
2020-02-11 19:23 ` Tim Walker [this message]
2020-03-03 16:40 ` Muhammad Ahmad
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='CANo=J14NY9TG9RAUMfX2N-q2ZCqiD0CGGVWu-DTgKJDQK20CRg@mail.gmail.com' \
--to=tim.t.walker@seagate.com \
--cc=david@fromorbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=muhammad.ahmad@seagate.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 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).