From: Matthias Schniedermeyer <ms@citd.de>
To: karn@ka9q.net
Cc: xfs@oss.sgi.com
Subject: Re: TRIM details
Date: Fri, 7 Jan 2011 10:17:20 +0100 [thread overview]
Message-ID: <20110107091720.GA6921@citd.de> (raw)
In-Reply-To: <20110107091120.GA6634@citd.de>
On 07.01.2011 10:11, Matthias Schniedermeyer wrote:
> On 06.01.2011 19:22, Phil Karn wrote:
>
> > Just have the drive interpret an ordinary write of all 0's to any LBA as
> > an implicit "unmap" indication for that LBA. As long as the drive
>
> The drive would have to look into each written sector in the off chance
> that it might be 0, that's a lot of electrons you have to burn for not
> much gain. And that's ignoring the performance side, doing such a check
> on each incoming write would be expensive at best.
Altough, after thinking about it a little more. Doing a Population count
in the controller while the data comes in over the wire can't be that
expensive.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-07 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 3:22 TRIM details Phil Karn
2011-01-07 4:35 ` Martin K. Petersen
2011-01-07 9:11 ` Matthias Schniedermeyer
2011-01-07 9:17 ` Matthias Schniedermeyer [this message]
2011-01-07 14:15 ` Phil Karn
2011-01-07 14:13 ` Phil Karn
2011-01-07 16:50 ` Martin K. Petersen
2011-01-07 23:43 ` Phil Karn
2011-01-07 14:21 ` Phil Karn
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=20110107091720.GA6921@citd.de \
--to=ms@citd.de \
--cc=karn@ka9q.net \
--cc=xfs@oss.sgi.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.