All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Gregoire Pichon <gregoire.pichon@bull.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH v4] staging: lustre: mdc: manage number of modify RPCs in flight
Date: Mon, 14 Nov 2016 16:17:37 +0100	[thread overview]
Message-ID: <20161114151737.GA18183@kroah.com> (raw)
In-Reply-To: <1478793073-21814-1-git-send-email-jsimmons@infradead.org>

On Thu, Nov 10, 2016 at 10:51:13AM -0500, James Simmons wrote:
> From: Gregoire Pichon <gregoire.pichon@bull.net>
> 
> This patch is the main client part of a new feature that supports
> multiple modify metadata RPCs in parallel. Its goal is to improve
> metadata operations performance of a single client, while maintening
> the consistency of MDT reply reconstruction and MDT recovery
> mechanisms.
> 
> It allows to manage the number of modify RPCs in flight within
> the client obd structure and to assign a virtual index (the tag) to
> each modify RPC to help server side cleaning of reply data.
> 
> The mdc component uses this feature to send multiple modify RPCs
> in parallel.

Is this a new feature?  Why should we take this now and not just wait
until the code is out of staging?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Gregoire Pichon <gregoire.pichon@bull.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH v4] staging: lustre: mdc: manage number of modify RPCs in flight
Date: Mon, 14 Nov 2016 16:17:37 +0100	[thread overview]
Message-ID: <20161114151737.GA18183@kroah.com> (raw)
In-Reply-To: <1478793073-21814-1-git-send-email-jsimmons@infradead.org>

On Thu, Nov 10, 2016 at 10:51:13AM -0500, James Simmons wrote:
> From: Gregoire Pichon <gregoire.pichon@bull.net>
> 
> This patch is the main client part of a new feature that supports
> multiple modify metadata RPCs in parallel. Its goal is to improve
> metadata operations performance of a single client, while maintening
> the consistency of MDT reply reconstruction and MDT recovery
> mechanisms.
> 
> It allows to manage the number of modify RPCs in flight within
> the client obd structure and to assign a virtual index (the tag) to
> each modify RPC to help server side cleaning of reply data.
> 
> The mdc component uses this feature to send multiple modify RPCs
> in parallel.

Is this a new feature?  Why should we take this now and not just wait
until the code is out of staging?

thanks,

greg k-h

  reply	other threads:[~2016-11-14 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 15:51 [lustre-devel] [PATCH v4] staging: lustre: mdc: manage number of modify RPCs in flight James Simmons
2016-11-10 15:51 ` James Simmons
2016-11-14 15:17 ` Greg Kroah-Hartman [this message]
2016-11-14 15:17   ` Greg Kroah-Hartman
2016-11-14 16:59   ` [lustre-devel] " James Simmons
2016-11-14 16:59     ` James Simmons
2016-11-14 17:20     ` [lustre-devel] " Greg Kroah-Hartman
2016-11-14 17:20       ` Greg Kroah-Hartman
2016-11-14 17:27       ` [lustre-devel] " James Simmons
2016-11-14 17:27         ` James Simmons
2016-11-15 10:03         ` [lustre-devel] " Greg Kroah-Hartman
2016-11-15 10:03           ` Greg Kroah-Hartman

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=20161114151737.GA18183@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregoire.pichon@bull.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.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.