linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, lsf10-pc@lists.linuxfoundation.org
Subject: Re: Current topics for LSF10/MM Summit 8-9 August in Boston
Date: Wed, 16 Jun 2010 23:35:16 -0700	[thread overview]
Message-ID: <1276756516.12514.272.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1276721459.2847.399.camel@mulgrave.site>

On Wed, 2010-06-16 at 15:50 -0500, James Bottomley wrote:
> Given that we're under two months out, I thought it would be time to
> post a summary of the topics we've collected so far (Nick will post the
> MM summit ones later).  Look this over, and if there's anything missing,
> propose it ... or if you have cross Storage/FS/MM topics, post them too.
> 
> Oh, and since we're not the most organised bunch, if you posted a topic
> and don't see it in the list, please resend ... we probably lost it in
> an email shuffle.
> 
> Current Filesystem Topics:
> 
> Alex Elder	Upstream maintainer for XFS, general discussion on FS/IO
> Aneesh Kumar	Rich-acl patches which work better with NFSv4 acl and CIFS acl
> Anshul Madan	reflink for NFS
> Chuck Lever	NFS/IPV6 and NFS O_DIRECT, Wu's read-ahead work, vitro perf tools
> Eric Sandeen	Advances in testing, TRIM/DISCARD/Alignment, writeback sanity
> James Lentini	reflink for NFS
> Jan Kara	Discuss/drive sanity review of writeback and general ext*/jbd 
> Michael Rubin	Writeback scaling
> Sage Weil	Statlite, generic interface for describing file striping for distributed FS, VFS scalability
> Al Viro	Sorting out d_revalidate and other dcache issues
> Coly Li		directory/large file scalability
> Sorin Faibish	Cache writeback discussion
> 
> Current Storage Topics:
> 
> Eric Seppanen	Next generation SSDs, performance implications on Linux I/O
> Boaz Harrosh	PNFS performance considerations, bio_list based/async raidN for generic use; stable pages for I/O
> FUJITA Tomonori	SCSI target mode, iSCSI, block layer SG (bsg), sg, IOMMU, DMA issues
> Hannes Reinecke	libfc/multipath/error handing
> James Smart	FCOE proposal for rework of the FC sysfs tree, work with Hannes on other transport/SCSI subsystem topics
> Jeff Moyer	IO scheduler
> Joel Becker	SAN management plugin
> Martin Petersen	Updates on DIF/DIX, TRIM/DISCARD/UNMAP, generic support for WRITE_SAME
> 
> Plus some MM summit ones which Nick will summarise.
> 

Greeting James and co,

I noticed that the bit wrt to the kernel level target mode fabric
independent configfs infrastructure is not mentioned in the above..

http://marc.info/?l=linux-scsi&m=127010303618447&w=2

Where would this best fit in..?

"A virtual filesystem driven by userspace syscalls to represent a target
HBA/DEV model on top upstream Linux storage subsystems for fabric
modules using a generic set of configfs struct config_groups to
represent target mode fabric endpoints (WWN+TPG+LUN) designed to allow
each their own set of fabric dependent attributes on top of a generic
kernel infrastructure.

The model is to allow the Linux VFS to handle the TCM core HBA/DEV logic
and both fabric independent and dependent data structure dependencies
between LKMs in order to simplify the conversion of existing and
creation of new target mode fabric code."

Best,

--nab


--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-17  6:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 20:50 Current topics for LSF10/MM Summit 8-9 August in Boston James Bottomley
2010-06-17  6:35 ` Nicholas A. Bellinger [this message]
2010-06-17 13:27   ` [Lsf10-pc] " James Bottomley
2010-06-17 16:00 ` Christof Schmitt
2010-06-17 16:07   ` James Bottomley
2010-06-17 16:13     ` Boaz Harrosh
2010-06-17 16:34     ` Vladislav Bolkhovitin
2010-06-17 16:42       ` James Bottomley
2010-06-17 17:11         ` Vladislav Bolkhovitin
2010-06-17 17:37           ` James Bottomley
2010-06-17 17:55             ` Vladislav Bolkhovitin
2010-06-18 11:41     ` Christof Schmitt
2010-06-18 12:18     ` [Lsf10-pc] " J. Bruce Fields
2010-06-21 12:05 ` Current MM " Nick Piggin
2010-06-21 13:16   ` [Lsf10-pc] " Andrea Arcangeli
2010-06-21 13:22     ` Gleb Natapov
2010-06-21 14:09       ` Andrea Arcangeli
2010-06-21 14:18         ` Gleb Natapov
2010-06-21 14:29           ` Andrea Arcangeli
2010-06-21 14:31             ` Avi Kivity
2010-06-21 14:45               ` Andrea Arcangeli
2010-06-22  3:30     ` KOSAKI Motohiro
2010-06-21 20:00   ` David Rientjes
2010-06-21 20:13     ` James Bottomley
2010-07-01 18:30   ` Larry Woodman
  -- strict thread matches above, loose matches on Subject: below --
2010-06-16 23:30 Current " James Bottomley

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=1276756516.12514.272.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --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;
as well as URLs for NNTP newsgroup(s).