Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>,
	Oleg Drokin <green@linuxhacker.ru>
Subject: [lustre-devel] [PATCH 0/2] Lustre fixes
Date: Wed, 16 Nov 2016 20:05:28 -0500	[thread overview]
Message-ID: <1479344730-1131617-1-git-send-email-green@linuxhacker.ru> (raw)

With multiple metadata RPCs code in now, these two fixes
become important.

Please consider.

Niu Yawei (2):
  staging/lustre/ptlrpc: track unreplied requests
  staging/lustre/ptlrpc: update imp_known_replied_xid on resend-replay

 .../staging/lustre/lustre/include/lustre_import.h  |   5 +
 drivers/staging/lustre/lustre/include/lustre_net.h |   3 +
 drivers/staging/lustre/lustre/obdclass/genops.c    |   2 +
 drivers/staging/lustre/lustre/ptlrpc/client.c      | 112 +++++++++++++++------
 drivers/staging/lustre/lustre/ptlrpc/import.c      |  34 +++++++
 drivers/staging/lustre/lustre/ptlrpc/niobuf.c      |  29 +++++-
 .../staging/lustre/lustre/ptlrpc/ptlrpc_internal.h |  24 +++++
 drivers/staging/lustre/lustre/ptlrpc/recover.c     |  14 +++
 8 files changed, 187 insertions(+), 36 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-11-17  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  1:05 Oleg Drokin [this message]
2016-11-17  1:05 ` [lustre-devel] [PATCH 1/2] staging/lustre/ptlrpc: track unreplied requests Oleg Drokin
2016-11-17  1:05 ` [lustre-devel] [PATCH 2/2] staging/lustre/ptlrpc: update imp_known_replied_xid on resend-replay Oleg Drokin

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=1479344730-1131617-1-git-send-email-green@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.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