All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org,
	vladimirk-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH 1/2] net/mlx5: increase async EQ to avoid EQ overrun
Date: Mon, 5 Feb 2018 11:09:04 -0700	[thread overview]
Message-ID: <20180205180904.GB11446@mellanox.com> (raw)
In-Reply-To: <1517840992-29813-1-git-send-email-maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On Mon, Feb 05, 2018 at 04:29:51PM +0200, Max Gurtovoy wrote:
> Currently the async EQ has 256 entries only. It might not be big enough
> for the SW to handle all the needed pending events. For example, in case
> of many QPs (let's say 1024) connected to a SRQ created using NVMeOF target
> and the target goes down, the FW will raise 1024 "last WQE reached" events
> and may cause EQ overrun. Increase the EQ to more reasonable size, that beyond
> it the FW should be able to delay the event and raise it later on using internal
> backpressure mechanism.

If the firmware has an internal backpressure meachanism then why
would we get a EQ overrun?

Do we need to block adding too many QPs to a SRQ as well or something
like that?

Jason
--
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

  parent reply	other threads:[~2018-02-05 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 14:29 [PATCH 1/2] net/mlx5: increase async EQ to avoid EQ overrun Max Gurtovoy
2018-02-05 14:29 ` [PATCH 2/2] net/mlx5: fix affinity mask for completion vectors Max Gurtovoy
2018-02-05 14:29   ` Max Gurtovoy
2018-02-05 14:36   ` Sagi Grimberg
     [not found] ` <1517840992-29813-1-git-send-email-maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-05 15:28   ` [PATCH 1/2] net/mlx5: increase async EQ to avoid EQ overrun Sagi Grimberg
2018-02-05 16:02   ` Doug Ledford
     [not found]     ` <1517846530.3936.71.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-02-05 16:10       ` Leon Romanovsky
2018-02-05 18:09   ` Jason Gunthorpe [this message]
     [not found]     ` <20180205180904.GB11446-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-05 23:11       ` Max Gurtovoy
     [not found]         ` <d572b570-0844-e441-19a0-e6804557fb58-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-05 23:16           ` Jason Gunthorpe
     [not found]             ` <20180205231617.GQ11446-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-08  5:45               ` Saeed Mahameed
     [not found]                 ` <CALzJLG9QQ_B4xj-E+HtpxUWZhFU9eWeqSNHSaQjf5HH=9TPXTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-08 16:26                   ` Jason Gunthorpe
     [not found]                     ` <20180208162605.GK9051-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-08 16:39                       ` Leon Romanovsky
2018-02-08 18:58                       ` Saeed Mahameed

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=20180205180904.GB11446@mellanox.com \
    --to=jgg-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org \
    --cc=vladimirk-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 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.