All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shirley Ma <shirley.ma@oracle.com>
To: Charles EDWARD Lever <chuck.lever@oracle.com>,
	"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
	"Devesh.Sharma@emulex.com" <Devesh.Sharma@emulex.com>,
	"dledford@redhat.com" <dledford@redhat.com>,
	"dominique.martinet@cea.fr" <dominique.martinet@cea.fr>,
	"jeffrey.c.becker@nasa.gov" <jeffrey.c.becker@nasa.gov>,
	"rsdance@soft-forge.com" <rsdance@soft-forge.com>,
	"skc@lanl.gov" <skc@lanl.gov>,
	"sprabhu@redhat.com" <sprabhu@redhat.com>,
	"SteveD@redhat.com" <SteveD@redhat.com>,
	"swise@opengridcomputing.com" <swise@opengridcomputing.com>,
	"wendy.cheng@intel.com" <wendy.cheng@intel.com>,
	"yanb@mellanox.com" <yanb@mellanox.com>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: NFSoRDMA bi-weekly developers meeting minutes (4/2)
Date: Thu, 02 Apr 2015 10:53:35 -0700	[thread overview]
Message-ID: <551D821F.5080006@oracle.com> (raw)

Attendees:

Yan Burman (Mellanox)
Steve Dickson (Red Hat)
Chuck Lever (Oracle)
Shirley Ma (Oracle)
Sachin Prabhu (RedHat)
Devesh Sharma (Emulex)
Anna Schumaker (Net App)
Steve Wise (OpenGridComputing, Chelsio)

Moderator:
Shirley Ma (Oracle)

Today's meeting notes:
Sorry for the late start, it has changed from 7:30am PST time to 8:30am PST time but I didn't notice the change wasn't sent out. :( Thanks for your patient to join the call one hour later.

1. NFSoRDMA deployment:
NFSoRDMA has much better performance than NFSoIPoIB-CM in general. People are looking for both Linux NFSoRDMA client and Server support for deployment, however distros only support NFSoRDMA client at this moment. Developers have been fixing bugs on server side, more dedicated resources on NFSoRDMA server development are needed for stability and performance work. We will continue to improve NFSoRDMA performance and try to find more resources on server side.

2. NFSoRDMA performance
After experimenting performance with different approaches (multiple QPs, different completion vector per QP), we think we should focus on single QP scalability first. Right now small I/O single QP IOPS is around 100K, large I/O single QP NFS READ can reach 3.6GB/s (which almost reaches link speed in the fabric). To identify single QP scalability, here are list of things we can try:
-- Generic RPC dispatching: identify serialized operations to make them paralleled
-- scheduling mechanism: wait_on_bit latency, queue work latency
-- RDMA transport layer: hack poll_cq on both client and server to make pulling longer, like wait for RPC RTT time, wait for more WCs to process more completions to reduce interrupts/wait overheads to see any better results

3. We will cover iSCSI/iSER/SRP in the future discussions.

10/23/2014
@8:30am PT DST
@9:30am MT DST
@10:30am CT DST
@11:30am ET DST
@Bangalore @9:00pm
@Israel @6:30pm

Duration: 1 hour

Call-in number:
Israel: +972 37219638
Bangalore: +91 8039890080 (180030109800)
France  Colombes +33 1 5760 2222    +33 176728936
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.

Shirley

WARNING: multiple messages have this Message-ID (diff)
From: Shirley Ma <shirley.ma-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Charles EDWARD Lever
	<chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	"Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org"
	<Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
	"Devesh.Sharma-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org"
	<Devesh.Sharma-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org>,
	"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"dominique.martinet-KCE40YydGKI@public.gmane.org"
	<dominique.martinet-KCE40YydGKI@public.gmane.org>,
	"jeffrey.c.becker-NSQ8wuThN14@public.gmane.org"
	<jeffrey.c.becker-NSQ8wuThN14@public.gmane.org>,
	"rsdance-rzwDkyJvnYokmLvzuZlaBw@public.gmane.org"
	<rsdance-rzwDkyJvnYokmLvzuZlaBw@public.gmane.org>,
	"skc-YOWKrPYUwWM@public.gmane.org"
	<skc-YOWKrPYUwWM@public.gmane.org>,
	"sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"SteveD-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<SteveD-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org"
	<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
	"wendy.cheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<wendy.cheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
	<yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux NFS Mailing List
	<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: NFSoRDMA bi-weekly developers meeting minutes (4/2)
Date: Thu, 02 Apr 2015 10:53:35 -0700	[thread overview]
Message-ID: <551D821F.5080006@oracle.com> (raw)

Attendees:

Yan Burman (Mellanox)
Steve Dickson (Red Hat)
Chuck Lever (Oracle)
Shirley Ma (Oracle)
Sachin Prabhu (RedHat)
Devesh Sharma (Emulex)
Anna Schumaker (Net App)
Steve Wise (OpenGridComputing, Chelsio)

Moderator:
Shirley Ma (Oracle)

Today's meeting notes:
Sorry for the late start, it has changed from 7:30am PST time to 8:30am PST time but I didn't notice the change wasn't sent out. :( Thanks for your patient to join the call one hour later.

1. NFSoRDMA deployment:
NFSoRDMA has much better performance than NFSoIPoIB-CM in general. People are looking for both Linux NFSoRDMA client and Server support for deployment, however distros only support NFSoRDMA client at this moment. Developers have been fixing bugs on server side, more dedicated resources on NFSoRDMA server development are needed for stability and performance work. We will continue to improve NFSoRDMA performance and try to find more resources on server side.

2. NFSoRDMA performance
After experimenting performance with different approaches (multiple QPs, different completion vector per QP), we think we should focus on single QP scalability first. Right now small I/O single QP IOPS is around 100K, large I/O single QP NFS READ can reach 3.6GB/s (which almost reaches link speed in the fabric). To identify single QP scalability, here are list of things we can try:
-- Generic RPC dispatching: identify serialized operations to make them paralleled
-- scheduling mechanism: wait_on_bit latency, queue work latency
-- RDMA transport layer: hack poll_cq on both client and server to make pulling longer, like wait for RPC RTT time, wait for more WCs to process more completions to reduce interrupts/wait overheads to see any better results

3. We will cover iSCSI/iSER/SRP in the future discussions.

10/23/2014
@8:30am PT DST
@9:30am MT DST
@10:30am CT DST
@11:30am ET DST
@Bangalore @9:00pm
@Israel @6:30pm

Duration: 1 hour

Call-in number:
Israel: +972 37219638
Bangalore: +91 8039890080 (180030109800)
France  Colombes +33 1 5760 2222    +33 176728936
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.

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:[~2015-04-02 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 17:53 Shirley Ma [this message]
2015-04-02 17:53 ` NFSoRDMA bi-weekly developers meeting minutes (4/2) Shirley Ma

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=551D821F.5080006@oracle.com \
    --to=shirley.ma@oracle.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=Devesh.Sharma@emulex.com \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=dledford@redhat.com \
    --cc=dominique.martinet@cea.fr \
    --cc=jeffrey.c.becker@nasa.gov \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rsdance@soft-forge.com \
    --cc=skc@lanl.gov \
    --cc=sprabhu@redhat.com \
    --cc=swise@opengridcomputing.com \
    --cc=wendy.cheng@intel.com \
    --cc=yanb@mellanox.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.