All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Don Brace <don.brace@microsemi.com>,
	"joseph.szczypek@hpe.com" <joseph.szczypek@hpe.com>,
	Gerry Morong <gerry.morong@microsemi.com>,
	John Hall <John.Hall@microsemi.com>,
	"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	Kevin Barnett <kevin.barnett@microsemi.com>,
	Mahesh Rajashekhara <mahesh.rajashekhara@microsemi.com>,
	Bader Ali - Saleh <bader.alisaleh@microsemi.com>,
	"hch@infradead.org" <hch@infradead.org>,
	Scott Teel <scott.teel@microsemi.com>,
	Viswas G <viswas.g@microsemi.com>,
	Justin Lindley <justin.lindley@microsemi.com>,
	Scott Benesh <scott.benesh@microsemi.com>,
	"POSWALD@suse.com" <POSWALD@suse.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 09/12] hpsa: separate monitor events from heartbeat worker
Date: Fri, 28 Apr 2017 09:06:39 +0200	[thread overview]
Message-ID: <1493363199.24450.1.camel@suse.com> (raw)
In-Reply-To: <4993A297653ECB4581FA5C3C31323D1951D38015@avsrvexchmbx2.microsemi.net>

On Thu, 2017-04-27 at 21:10 +0000, Don Brace wrote:
> > -
> > The new worker thread duplicates code from hpsa_rescan_ctlr_worker.
> > I
> > find this a bit irritating. Could you maybe use just a single
> > worker,
> > and just check using time stamps whether the "big" heartbeat needs
> > to
> > be performed?
> > 
> > Regards
> > Martin
> > 
> > --
> > Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
> > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham
> > Norton
> > HRB 21284 (AG Nürnberg)
> 
> We thought about that, but we want to separate controller events
> from the rescan worker.
> 
> Both can cause a rescan to occur however for multipath we have
> found that we need to respond faster than the normal scheduled rescan
> interval for path fail-overs.
> 
> Getting controller events only involves reading a register, but
> the rescan worker can obtain an updated LUN list when there
> is a PTRAID device present.
> 
> However, I did refactor the patch to move common code to
> a separate function.
> 
> Would this be more acceptable?

Sounds good, yes. I'd also appreciate if you'd add these additional
comments to the commit message.

Regards
Martin

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

  reply	other threads:[~2017-04-28  7:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 20:05 [PATCH 00/12] hpsa updates Don Brace
2017-04-07 20:05 ` [PATCH 01/12] hpsa: update identify physical device structure Don Brace
2017-04-07 20:05 ` [PATCH 02/12] hpsa: do not get enclosure info for external devices Don Brace
2017-04-07 20:06 ` [PATCH 03/12] hpsa: update reset handler Don Brace
2017-04-07 20:06 ` [PATCH 04/12] hpsa: do not reset enclosures Don Brace
2017-04-07 20:06 ` [PATCH 05/12] hpsa: rescan later if reset in progress Don Brace
2017-04-07 20:06 ` [PATCH 06/12] hpsa: correct resets on retried commands Don Brace
2017-04-07 20:06 ` [PATCH 07/12] hpsa: cleanup reset handler Don Brace
2017-04-11 12:35   ` Martin Wilck
2017-04-26 19:01     ` Don Brace
2017-04-07 20:06 ` [PATCH 08/12] hpsa: correct queue depth for externals Don Brace
2017-04-07 20:06 ` [PATCH 09/12] hpsa: separate monitor events from heartbeat worker Don Brace
2017-04-11 12:18   ` Martin Wilck
2017-04-27 21:10     ` Don Brace
2017-04-28  7:06       ` Martin Wilck [this message]
2017-04-07 20:06 ` [PATCH 10/12] hpsa: send ioaccel requests with 0 length down raid path Don Brace
2017-04-07 20:06 ` [PATCH 11/12] hpsa: remove abort handler Don Brace
2017-04-07 20:06 ` [PATCH 12/12] hpsa: bump driver version Don Brace

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=1493363199.24450.1.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=John.Hall@microsemi.com \
    --cc=POSWALD@suse.com \
    --cc=bader.alisaleh@microsemi.com \
    --cc=don.brace@microsemi.com \
    --cc=gerry.morong@microsemi.com \
    --cc=hch@infradead.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=joseph.szczypek@hpe.com \
    --cc=justin.lindley@microsemi.com \
    --cc=kevin.barnett@microsemi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mahesh.rajashekhara@microsemi.com \
    --cc=scott.benesh@microsemi.com \
    --cc=scott.teel@microsemi.com \
    --cc=viswas.g@microsemi.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.