DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Svein Tonning <svein.tonning@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Performance with SSD with TRIM in mind?
Date: Fri, 26 Mar 2010 12:37:33 +0100	[thread overview]
Message-ID: <4BAC9C7D.3040900@redhat.com> (raw)
In-Reply-To: <c92bb2911003260334i287890baq3ac74f33aa6c9ade@mail.gmail.com>

On 03/26/2010 11:34 AM, Svein Tonning wrote:
> Tomorrow I will upgrade my laptop. With and SSD. My question is does
> luks/the-encryption destroy the TRIM functionality? 
> Because ext4 is suppose to talk to kernel, and the kernel then issues
> the trim command to the hdd. ext4 is on top of the encryption. 
> That is why i'm asking. 

Currently device-mapper (thus dm-crypt too) have no TRIM support,
but it is planned to be implemented (soon). no ETA yet, sorry.
So it will work but without TRIM support.

Milan

      reply	other threads:[~2010-03-26 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 10:34 [dm-crypt] Performance with SSD with TRIM in mind? Svein Tonning
2010-03-26 11:37 ` Milan Broz [this message]

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=4BAC9C7D.3040900@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=svein.tonning@gmail.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