From: <Mark_Ruder@Dell.com>
To: James.Bottomley@HansenPartnership.com
Cc: lsf10-pc@lists.linuxfoundation.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-scsi@vger.kernel.org
Subject: RE: [Lsf10-pc] Suggested topic for August LSF summit event (SCSI/FS/MM)
Date: Fri, 18 Jun 2010 10:29:16 -0500 [thread overview]
Message-ID: <F8ACFB06B9FB33429F1F0A8D62A89BAA085F53A2D5@AUSX7MCPS303.AMER.DELL.COM> (raw)
In-Reply-To: <1276873901.2850.40.camel@mulgrave.site>
Resending as text.
SAN Storage Features affecting the Kernel
● ISCSI Array Multipathing
● LUN split over several arrays. Separate data connection to
each array for parts of the LUN
● Requires kernel iSCSI path selector module per-vendor
● Thin Provisioning
● Actual allocated storage is less than requested size (akin to
sparse files)
● Must handle alerts when TP threshholds reached
– CHECK CONDITION raised on writes
– LUN goes read-only if space exhausted
● T10 work ongoing to standardize interfaces and behavior
● TRIM / UNMAP / WRITE_SAME
● Inform storage that these blocks are no longer needed
● Useful on SANs, not just SSDs
● T10 & T13 standards proposals in flux
● XCOPY – Array-level block copy, perhaps copy-on-write
● Copy blocks w/o incuring network and CPU overhead
● VFS function?
● T10 standard already (SCSI Extended Copy)
SAN Storage Features needing basic CLI work
● Multi-IQN – iSCSI IQNs are assigned to Guest VMs
● Implemented in iscsi-initiator-utils today, thank you!
● VM Guest boot from iSCSI
● Requires iSCSI Initiator in VM BIOS
● Fedora 11 KVM will load gPXE iSCSI Option ROMs, thank
you!
● Array-based LUN snapshots
● ioctl(FIFREEZE) added Jan 09 by Takashi Sato of NEC,
thank you!
● Need CLI to freeze file system, issue array-based snapshot
command, and thaw file system
Thanks,
Mark
-----Original Message-----
From: James Bottomley [mailto:James.Bottomley@HansenPartnership.com]
Sent: Friday, June 18, 2010 10:12 AM
To: Ruder, Mark
Cc: lsf10-pc@lists.linuxfoundation.org; linux-fsdevel@vger.kernel.org; linux-mm@kvack.org; linux-scsi@vger.kernel.org
Subject: Re: [Lsf10-pc] Suggested topic for August LSF summit event (SCSI/FS/MM)
On Fri, 2010-06-18 at 09:55 -0500, Mark_Ruder@Dell.com wrote:
> I was asked to share suggested topics that we would be interested in
> being discussed in the upcoming LSF Summit even in early August.
> Rather that re-typing all of them into this email, I’ve attached a
> slide deck developed by Matt Domsch in Dell’s CTO office as a starting
> point. It is a bit dated, but we feel that topics are still relevant
> to us.
We got this on the PC lists, but all of the other mailing lists will
have discarded it sight unseen (enforcing plain text only and nothing
other than text/plain attachments is a standard list spam mitigation
technique). Could you summarise as text (you can just go to the outline
view and paste everything into a text window).
James
prev parent reply other threads:[~2010-06-18 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F8ACFB06B9FB33429F1F0A8D62A89BAA085F53A240@AUSX7MCPS303.AMER.DELL.COM>
2010-06-18 15:11 ` James Bottomley
2010-06-18 15:21 ` Mark_Ruder
2010-06-18 15:29 ` Mark_Ruder [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=F8ACFB06B9FB33429F1F0A8D62A89BAA085F53A2D5@AUSX7MCPS303.AMER.DELL.COM \
--to=mark_ruder@dell.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.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