xfs
[Top] [All Lists]

Re: XFS journaling position

To: xfs@xxxxxxxxxxx
Subject: Re: XFS journaling position
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 28 Oct 2010 11:44:38 +0200
Cc: Robert Brockway <robert@xxxxxxxxxxxxxxxxx>
In-reply-to: <alpine.DEB.1.10.1010271027511.27409@xxxxxxxxxxxxxxxxxxxx>
Organization: it-management http://it-management.at
References: <31c7e56286d37870011c17ee8e002760.squirrel@xxxxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.1010271011510.27409@xxxxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.1010271027511.27409@xxxxxxxxxxxxxxxxxxxx>
User-agent: KMail/1.13.5 (Linux/2.6.34.7-0.4-desktop; KDE/4.4.4; x86_64; ; )
On Mittwoch, 27. Oktober 2010 Robert Brockway wrote:
> Similarly virtual hosts have little chance of trying to establish
> the  physical nature of the device holding their filesystems.

Yes, performance optimizations will be fun in the near future. VMs, thin 
provisioning, NetApps WAFL, LVM, funny disk layouts, all can do things 
completely different than our "old school" thinking. I wonder when 
there's gonna be an I/O scheduler that just elevates the I/O from a VM 
to the real host, so that the host itself can optimize and align. After 
all, a VM has no idea of the storage. That's why already now you can 
choose "noop" as the scheduler in a VM. I guess there will be a 
"virtualized" scheduler once, but we will see.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

Attachment: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>