All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goetz Bock <bock@blacknet.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] RFC: DM encryption target?
Date: Mon Sep 29 08:07:05 2003	[thread overview]
Message-ID: <20030926214616.GG12384@shell.blacknet.de> (raw)
In-Reply-To: <1064581467.4175.3.camel@chtephan.cs.pocnet.net>

On Fri, Sep 26 '03 at 15:04, Christophe Saout wrote:
> Am Fr, den 26.09.2003 schrieb jon+lvm@silicide.dk um 14:48:
> 
> > > I don't know, but couldn't the use of a one-sector block slow things
> > > down because of alignment issues? Perhaps using a 4k block would be more
> > > useful or storing the sector at the end of the device (like the linux
> > > raid info sector).
> > 
> > maybe, but does it matter? 
> 
> No, I meant the following: Let's assume you are using crypto on a raid
> 0/5 device or something. Usually the filesystem uses 4k blocks. 
> [ ... ] A lot of harddisks these days use internal blocks that are
> larger than 512 bytes so there are also alignment issues.
While I don't have any idea how harddisks work internaly thise days,
I've no problem to loose 4k or even 16k if it improves anything. 
But I would still like to get it to the beginning of the
partition/drive/device.

Mainly to be able to do

less -f $DEVICE

to figure out what it's all about. I do this more often than not and
hate it if all i get back is just binary garbage. 

Everyfile should tell me what is is for/from in plain text. 
-- 
/"\ Goetz Bock at blacknet dot de  --  secure mobile Linux everNETting
\ /                     (c) 2003 as GNU FDL 1.1
 X   [ 1. Use descriptive subjects - 2. Edit a reply for brevity -  ]
/ \  [ 3. Reply to the list - 4. Read the archive *before* you post ]

  reply	other threads:[~2003-09-29  8:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 11:02 [linux-lvm] DM encryption target? Greg Freemyer
2003-09-23 12:08 ` Kevin Corry
2003-09-23 11:55   ` Greg Freemyer
2003-09-23 14:02 ` Christophe Saout
2003-09-24  6:21   ` Jon Bendtsen
2003-09-24  7:00     ` Christophe Saout
2003-09-24  9:53       ` jon+lvm
2003-09-25  8:03       ` Goetz Bock
2003-09-25 11:09         ` [linux-lvm] RFC: " Christophe Saout
2003-09-26  7:50           ` jon+lvm
2003-09-26  8:05             ` Christophe Saout
2003-09-29  8:07               ` Goetz Bock [this message]
2003-09-29  8:40                 ` jon+lvm
2003-09-26 14:16             ` Greg Freemyer
2003-09-27  8:35               ` jon+lvm

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=20030926214616.GG12384@shell.blacknet.de \
    --to=bock@blacknet.de \
    --cc=linux-lvm@sistina.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.