public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Shirley Ma <shirley.ma-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Jeff Becker <jeffrey.c.becker-NSQ8wuThN14@public.gmane.org>,
	"<yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>"
	<yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"Cayton,
	Phil" <phil.cayton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Coulter, Susan K" <skc-YOWKrPYUwWM@public.gmane.org>,
	Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	Anna Schumaker
	<Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
	"<Devesh.Sharma-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org>"
	<Devesh.Sharma-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org>,
	Steve Wise
	<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
	Allen Andrews
	<Allen.Andrews-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org>,
	Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org,
	"<emossman-zcUZCMB5SQOVc3sceRu5cw@public.gmane.org>"
	<emossman-zcUZCMB5SQOVc3sceRu5cw@public.gmane.org>
Subject: NFSoRDMA developers bi-weekly meeting announcement (4/30)
Date: Wed, 30 Apr 2014 12:16:19 -0700	[thread overview]
Message-ID: <53614C03.80606@oracle.com> (raw)

Attendees:
Jeff Beck (NASA)
Yan Burman (Mellanox)
Phil Cayton (Intel)
Susan Coulter (LANL)
Chuck Lever (Oracle)
Shirley Ma (Oracle)
Anna Schumaker (Net App)
Devesh Sharma (Emulex)
Steve Wise (OpenGridComputing, Chelsio)

Moderate:
Shirley Ma (Oracle)

4/30/2014 meeting summaries:
NFSoRDMA developers bi-weekly meeting is to help organizing NFSoRDMA 
development and test effort from different resources to speed up 
NFSoRDMA upstream kernel work and NFSoRDMA diagnosing/debugging tools 
development. Hopefully the quality of NFSoRDMA upstream patches can be 
improved by being tested by a quorum of HW vendors. The NFSoRDMA issues 
can be tracked and followed up in time.

Today's meeting covered:
1. NFSoRDMA test strategy and plan:
What NFS related software tools are available for functional and 
performance test?
Chuck has created a wiki page for NFSoRDMA test. The wiki page covers 
NFSoRDMA functionality, stress and performance test. Here is the link to 
the wiki:

http://wiki.linux-nfs.org/wiki/index.php/NfsRdmaClient/Home#Submitting_patches 


If you have any other test suggestions like scalability test, please 
send to Chuck Lever.

How are we going to organize continuous testing resources:
Each of us have our own lab with different configuration, thus we could 
have a better test coverage without purchasing/installing all vendors 
hardware.

2. Helping others on problem report and follow up:
How to get help from the communities?
Problems should be reported on both linux-nfs and linux-rdma mailing 
list. However some others found the problems they reported had been 
ignored in the past. In order to better tracking NFSoRDMA bug report, we 
have created NFSoRDMA linux-nfs.org bugzilla family, which will be 
mirrored to liux-nfs, linux-rdma mailing list. Here is the link to 
linux-nfs.org NFSoRDMA bugzilla:

https://bugzilla.linux-nfs.org/enter_bug.cgi?product=kernel

NFSoRDMA server component: svcrdma
NFSoRDMA client component: xprtrdma

Chuck Lever and Shirley Ma will help tracking issues on NFSoRDMA bugs. 
This isn't guaranteed the bugs being assigned and fixed. Chuck Lever and 
Shirley Ma will work on NFSoRDMA client side issues. But we still 
couldn't locate resources to support NFSoRDMA server. This is an 
outstanding issue.

3. Upstream NFSoRDMA status:
Anna Schumaker has created git tree to maintain all NFSoRDMA client 
stable patches. It will be easy for maintainer to pull patches to 
upstream. NFSoRDMA end users can use her git tree. Here is the link to 
Anna's NFSoRDMA client git tree:

git://git.linux-nfs.org/projects/anna/nfs-rdma.git

Chuck Lever's NFSoRDMA linux-nfs.org git tree is for developers only. 
All patches should be reviewed and tested before going to Anna's tree. 
Here is link to Chuck Lever's git tree, check out nfs-rdma-client branch.

git://git.linux-nfs.org/projects/cel/cel-2.6.git

4. NFSoRDMA debugging and diagnosis tools:
ibdump is a ConnectX sniffing tool, which can be used to monitor 
InfiniBand packets on the fabrics. wireshark is able to interpret these 
packets in IB but not NFSoRDMA layer. A dissector is needed for NFSoRDMA 
protocol. Yan Burman will look at how much work to create NFSoRDMA 
dissector for wireshark.

Chelsio is also able to replicate packets to other interface for 
wireshark to monitor. Steve Wise will help on finding how-to instruction.

Next meeting topics proposal:
1. Follow up the work has been discussed from this meeting.

2. Walk through some of the stories on pivotal, link is as below:
https://www.pivotaltracker.com/s/projects/958376

3. Invite some of the developers to discuss some of their requirements 
and features.

Meeting time: one hour discussion every other Wed (next meeting will be 
on 5/14). A reminder will be sent out to both linux-nfs and linux-rdma 
mailing list:

5/14/2014
@8:00am PST
@9:00am MST
@10:00am CST
@11:00am EST
@Bangalore @9:00pm
@Israel @6:00pm

Duration: 1 hour

Call-in number:
Israel: +972 37219638
Bangalore: +91 8039890080 (180030109800)
US: 8666824770,  408-7744073
Conference Code: 2308833
Passcode: 63767362 (it's NFSoRDMA, in case you couldn't remember)

Thanks everyone for joining the call and providing valuable inputs/work 
to the community to make NFSoRDMA better. Anyone who are interested in 
NFSoRDMA is welcome to join the incoming meetings on 5/14.

Shirley
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-04-30 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 19:16 Shirley Ma [this message]
     [not found] ` <53614C03.80606-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-04-30 19:39   ` NFSoRDMA developers bi-weekly meeting announcement (4/30) Or Gerlitz
     [not found]     ` <CAJZOPZJioYdcbDGsk7278sZS7kD9W1dcGEGtYfsFk=Mm7DW3fQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-30 19:47       ` Chuck Lever
     [not found]         ` <BBF761A6-2407-4457-92D5-8C2EC736BC9D-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-04-30 20:00           ` Or Gerlitz
     [not found]             ` <CAJZOPZJgp-QdxR+PmwACWOSc4h_167J0iBjfmMrPX8sek600WA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-30 20:49               ` Shirley Ma
     [not found]                 ` <536161D0.3000600-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-04-30 23:58                   ` Doug Ledford
2014-04-30 23:58                   ` Doug Ledford
     [not found]                 ` <30686627.1636.1398902288314.JavaMail."Doug Ledford"@Phenom>
2014-05-01  5:16                   ` Shirley Ma
     [not found]                     ` <5361D89F.4070503-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-05-01 16:03                       ` Doug Ledford
2014-05-01 16:03                       ` Doug Ledford

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=53614C03.80606@oracle.com \
    --to=shirley.ma-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=Allen.Andrews-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org \
    --cc=Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
    --cc=Devesh.Sharma-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org \
    --cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=emossman-zcUZCMB5SQOVc3sceRu5cw@public.gmane.org \
    --cc=jeffrey.c.becker-NSQ8wuThN14@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=phil.cayton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=skc-YOWKrPYUwWM@public.gmane.org \
    --cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
    --cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
    --cc=yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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