From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] [ATTEND] Future writeback topics
Date: Mon, 23 Jan 2012 00:11:06 +0200 [thread overview]
Message-ID: <4F1C897A.3070401@panasas.com> (raw)
In-Reply-To: <1327247393.2834.15.camel@dabdike.int.hansenpartnership.com>
On 01/22/2012 05:49 PM, James Bottomley wrote:
>
> But this topic then becomes adding alignment for non block backed
> filesystems? I take it you're thinking NFS rather than MTD or MMC?
>
Sorry to differ. But no this is for most making the IO aligned in the first
place. Block-dev or not. Today VFS has no notion of alignment and IO is
submitted as is with out any alignment considerations.
> For multiple devices, you do a simple cascade ... a bit like dm does
> today ... but unless all the devices are aligned to optimal I/O it never
> really works (and it's not necessarily worth solving ... the idea that
> if you want performance from an array of devices, you match
> characteristics isn't a hugely hard one to get the industry to swallow).
>
No I'm talking about raid configurations like object raid in exofs/NFS or
raid0/5 in BTRFS and ZFS and such, where there are other larger alignment
structures to consider. Also for large-blocks filesystems/devices who
would like IO aligned on bigger than a page sizes.
Thanks
Boaz
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
<lsf-pc@lists.linux-foundation.org>, <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] [ATTEND] Future writeback topics
Date: Mon, 23 Jan 2012 00:11:06 +0200 [thread overview]
Message-ID: <4F1C897A.3070401@panasas.com> (raw)
In-Reply-To: <1327247393.2834.15.camel@dabdike.int.hansenpartnership.com>
On 01/22/2012 05:49 PM, James Bottomley wrote:
>
> But this topic then becomes adding alignment for non block backed
> filesystems? I take it you're thinking NFS rather than MTD or MMC?
>
Sorry to differ. But no this is for most making the IO aligned in the first
place. Block-dev or not. Today VFS has no notion of alignment and IO is
submitted as is with out any alignment considerations.
> For multiple devices, you do a simple cascade ... a bit like dm does
> today ... but unless all the devices are aligned to optimal I/O it never
> really works (and it's not necessarily worth solving ... the idea that
> if you want performance from an array of devices, you match
> characteristics isn't a hugely hard one to get the industry to swallow).
>
No I'm talking about raid configurations like object raid in exofs/NFS or
raid0/5 in BTRFS and ZFS and such, where there are other larger alignment
structures to consider. Also for large-blocks filesystems/devices who
would like IO aligned on bigger than a page sizes.
Thanks
Boaz
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-01-22 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 13:50 [LSF/MM TOPIC] [ATTEND] Future writeback topics Boaz Harrosh
2012-01-22 13:50 ` Boaz Harrosh
2012-01-22 14:49 ` James Bottomley
2012-01-22 15:37 ` Boaz Harrosh
2012-01-22 15:37 ` Boaz Harrosh
2012-01-22 15:49 ` [Lsf-pc] " James Bottomley
2012-01-22 22:11 ` Boaz Harrosh [this message]
2012-01-22 22:11 ` Boaz Harrosh
2012-01-22 15:27 ` James Bottomley
2012-01-23 12:33 ` Johannes Weiner
2012-01-23 12:33 ` Johannes Weiner
2012-01-23 13:41 ` Boaz Harrosh
2012-01-23 13:41 ` Boaz Harrosh
2012-01-23 18:15 ` Jan Kara
2012-01-23 20:19 ` [Lsf-pc] " Vivek Goyal
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=4F1C897A.3070401@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aarcange@redhat.com \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.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.