All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Desai <kashyap.desai@broadcom.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-scsi@vger.kernel.org, Peter Rivera <peter.rivera@broadcom.com>
Subject: RE: [RFC 1/2] mpt3sas/megaraid_sas : irq poll to avoid CPU hard and soft lockups
Date: Mon, 15 Jan 2018 18:00:31 +0530	[thread overview]
Message-ID: <b9ee2a9a5429f56b5ead8e6197a3bc84@mail.gmail.com> (raw)
In-Reply-To: <20180115121919.ux3owxg7fozfmnv7@linux-x5ow.site>

> -----Original Message-----
> From: Johannes Thumshirn [mailto:jthumshirn@suse.de]
> Sent: Monday, January 15, 2018 5:49 PM
> To: Kashyap Desai
> Cc: linux-scsi@vger.kernel.org; Peter Rivera
> Subject: Re: [RFC 1/2] mpt3sas/megaraid_sas : irq poll to avoid CPU hard
and
> soft lockups
>
> On Mon, Jan 15, 2018 at 05:42:35PM +0530, Kashyap Desai wrote:
> > Patch for Fix-1 explained in PATCH 0.
>
> Ahm, PATCH 0 a.k.a the cover letter doesn't get merged so the git
history
> won't have an explanation at all. Please write a proper commit message.

For now I am looking for input from linux community regarding approach
used in my solution.
I will convert RFC to PATCH and most suitable header I will attach with
each patch. Hope it is OK.

Current RFC has changes included for mpt3sas. Same logic will be followed
for megaraid_sas as well. Just for reference I have posted changes of
mpt3sas and not included megaraid_sas.


>
> Thanks,
> 	Johannes
>
> --
> Johannes Thumshirn                                          Storage
> jthumshirn@suse.de                                +49 911 74053 689
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
> GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG
> Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76
> 0850

      reply	other threads:[~2018-01-15 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 12:12 [RFC 1/2] mpt3sas/megaraid_sas : irq poll to avoid CPU hard and soft lockups Kashyap Desai
2018-01-15 12:19 ` Johannes Thumshirn
2018-01-15 12:30   ` Kashyap Desai [this message]

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=b9ee2a9a5429f56b5ead8e6197a3bc84@mail.gmail.com \
    --to=kashyap.desai@broadcom.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=peter.rivera@broadcom.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.