public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gentoo on a Dell XPS 13 Ultrabook
Date: Mon, 5 Mar 2012 08:58:08 +0700	[thread overview]
Message-ID: <CAA2qdGWU3iGzMNynesmCQKxFMrMHMV-TeC4sS74fc1oCxY6w-g@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw2Z5=FMXgrxRo5bbO4ewj4xo4Lf8o4uXUdutvyvbc_DrA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]

On Mar 5, 2012 3:15 AM, "Grant" <emailgrant@gmail.com> wrote:
>
> [snip]
> >> HOWEVER, make sure that all partitions begin at multiples of 8 (e.g.,
64,
> >> 72, 80, and so on); this will save you a lot of grief if it happens
that the
> >> hard disk you're using has 4KiB-sectors. [1]
> >
> > <snip the rest>
> >
> > From what I recall of looking at that toy's specs, it's running on an
> > SSD, so it becomes even more important, performance-wise, to have
> > things aligned properly so any one write doesn't cause two full erase
> > blocks to be cycled. The 1MB alignment is, if I recall, a balance
> > Microsoft struck as the midpoint between multiple hardware vendors to
> > work well on any of them... raid arrays, SSDs, advanced format hard
> > drives with 4k sectors on-disk, etc.
>
> Just to confirm, starting at block 2048 is OK?
>

No problem. You'll just be shortchanged of almost 1MiB. Nothing to lose
sleep over, IMO.

The most important thing is to make sure that *all* partitions begin on
sectors divisible by 8. So, if you're going to set up multiple partitions,
eyeball their start sectors carefully.

Rgds,

[-- Attachment #2: Type: text/html, Size: 1423 bytes --]

  parent reply	other threads:[~2012-03-05  2:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  2:12 [gentoo-user] Gentoo on a Dell XPS 13 Ultrabook Grant
2012-03-02  8:01 ` Alan McKinnon
2012-03-02 20:29   ` Grant
2012-03-02 23:03     ` Neil Bothwick
2012-03-02 23:35       ` Grant
2012-03-02 23:05 ` [gentoo-user] " walt
2012-03-02 23:39   ` Grant
2012-03-03 17:50     ` Grant
2012-03-03 18:13       ` Pandu Poluan
2012-03-03 18:15         ` Pandu Poluan
2012-03-03 18:22           ` Pandu Poluan
2012-03-03 18:24             ` Pandu Poluan
2012-03-03 20:12         ` Joshua Murphy
2012-03-04 20:12           ` Grant
2012-03-04 20:34             ` Alex Schuster
2012-03-05  1:53               ` Pandu Poluan
2012-03-05 13:40                 ` Alex Schuster
2012-03-05  1:58             ` Pandu Poluan [this message]
2012-03-04 20:02         ` Grant
2012-03-04 20:06           ` Grant
2012-03-04 21:09         ` Grant
2012-03-04 21:45           ` Mark Knecht
2012-03-04 21:56             ` Grant
2012-03-04 22:07               ` Alan McKinnon
2012-03-04 22:36                 ` Grant
2012-03-05  2:19                   ` Pandu Poluan
2012-03-05  2:12                 ` Pandu Poluan
2012-03-05  2:06               ` Pandu Poluan
2012-03-05 21:41                 ` Mark Knecht
2012-03-05 16:00               ` Alex Schuster
2012-03-05 16:33                 ` Pandu Poluan
2012-03-05 20:17                   ` Alan McKinnon
2012-03-05 21:33                 ` Joshua Murphy

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=CAA2qdGWU3iGzMNynesmCQKxFMrMHMV-TeC4sS74fc1oCxY6w-g@mail.gmail.com \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.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