linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Hubert Kario <hka@qbs.com.pl>
Cc: Chris Mason <chris.mason@oracle.com>,
	Gordan Bobic <gordan@bobich.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: SSD Optimizations
Date: Sat, 13 Mar 2010 18:02:10 +0100	[thread overview]
Message-ID: <20100313180210.4eb1b705.skraw@ithnet.com> (raw)
In-Reply-To: <201003121700.09553.hka@qbs.com.pl>

On Fri, 12 Mar 2010 17:00:08 +0100
Hubert Kario <hka@qbs.com.pl> wrote:
> > Even on true
> > spinning disks your assumption is wrong for relocated sectors.
> 
> Which we don't have to worry about because if the drive has less than 5 of 
> 'em, the impact of hitting them is marginal and if there are more, the user 
> has much more pressing problem than the performance of the drive or FS.

Are you really sure that a drive firmware tells you about the true number of
relocated sectors? I mean if it makes the product look better in comparison to
another product, are you really sure that the firmware will not tell you what
you expect to see only to make you content and happy with your drive?

> > Which
> > basically means that every disk controller firmware fiddles around with
> > the physical layout since decades. Please accept that you cannot do a
> > disks' job in FS. The more advanced technology gets the more disks become
> > black boxes with a defined software interface. Use this interface and drop
> > the idea of having inside knowledge of such a device. That's other
> > peoples' work. If you want to design smart SSD controllers hire at a
> > company that builds those.
> 
> And I don't think that doing disks' job in the FS is good idea, but I think 
> that we should be able to minimise the impact of the translation layer.
> 
> The way to do this, is to threat the device as a block device with sectors the 
> size of erase-blocks. That's nothing too fancy, don't you think?

I don't believe anyone is able to tell the size of erase-blocks of some device
- current and future - for sure. I do believe that making this guess only
reduces the future design options for new devices - if its creators care at
all about your guess.
Why not let the fs designer take his creative options in fs layer and let the
device designer use his brain on the device level and all meet at the
predefined software interface in between - and nowhere _else_.


> -- 
> Hubert Kario

-- 
Regards,
Stephan

  reply	other threads:[~2010-03-13 17:02 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 19:49 SSD Optimizations Gordan Bobic
2010-03-10 21:14 ` Marcus Fritzsch
2010-03-10 21:22   ` Marcus Fritzsch
2010-03-10 23:13   ` Gordan Bobic
2010-03-11 10:35     ` Daniel J Blueman
2010-03-11 12:03       ` Gordan Bobic
2010-03-10 23:12 ` Mike Fedyk
2010-03-10 23:22   ` Gordan Bobic
2010-03-11  7:38     ` Sander
2010-03-11 10:59       ` Hubert Kario
2010-03-11 11:31         ` Stephan von Krawczynski
2010-03-11 12:17           ` Gordan Bobic
2010-03-11 12:59             ` Stephan von Krawczynski
2010-03-11 13:20               ` Gordan Bobic
2010-03-11 14:01                 ` Hubert Kario
2010-03-11 15:35                   ` Stephan von Krawczynski
2010-03-11 16:03                     ` Gordan Bobic
2010-03-11 16:19                       ` Chris Mason
2010-03-12  1:07                         ` Hubert Kario
2010-03-12  1:42                           ` Chris Mason
2010-03-12  9:15                           ` Stephan von Krawczynski
2010-03-12 16:00                             ` Hubert Kario
2010-03-13 17:02                               ` Stephan von Krawczynski [this message]
2010-03-13 19:01                                 ` Hubert Kario
2010-03-11 16:48             ` Martin K. Petersen
2010-03-11 14:39           ` Sander
2010-03-11 17:35             ` Stephan von Krawczynski
2010-03-11 18:00               ` Chris Mason
2010-03-13 16:43                 ` Stephan von Krawczynski
2010-03-13 19:41                   ` Hubert Kario
2010-03-13 21:48                   ` Chris Mason
2010-03-14  3:19                   ` Jeremy Fitzhardinge
2010-03-11 12:09         ` Gordan Bobic
2010-03-11 16:22           ` Martin K. Petersen
2010-03-11 11:59       ` Gordan Bobic
2010-03-11 15:59         ` Asdo
     [not found]         ` <4B98F350.6080804@shiftmail.org>
2010-03-11 16:15           ` Gordan Bobic
2010-03-11 14:21 ` Chris Mason
2010-03-11 16:18   ` Gordan Bobic
2010-03-11 16:29     ` Chris Mason
  -- strict thread matches above, loose matches on Subject: below --
2010-12-12 17:24 SSD optimizations Paddy Steed
2010-12-13  0:04 ` Gordan Bobic
2010-12-13  5:11   ` Sander
2010-12-13  9:25     ` Gordan Bobic
2010-12-13 14:33       ` Peter Harris
2010-12-13 15:04         ` Gordan Bobic
2010-12-13 15:17       ` cwillu
2010-12-13 16:48         ` Gordan Bobic
2010-12-13 17:17   ` Paddy Steed
2010-12-13 17:47     ` Gordan Bobic
2010-12-13 18:20     ` Tomasz Torcz
2010-12-13 19:34       ` Ric Wheeler

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=20100313180210.4eb1b705.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=chris.mason@oracle.com \
    --cc=gordan@bobich.net \
    --cc=hka@qbs.com.pl \
    --cc=linux-btrfs@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 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).