DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@nvidia.com>
To: Yaron Illouz <yaroni@radcom.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: mellanox connect x 5 drops when cache full
Date: Thu, 20 Jan 2022 12:58:45 +0000	[thread overview]
Message-ID: <BL1PR12MB53803F145BD0598DCEE9C618DF5A9@BL1PR12MB5380.namprd12.prod.outlook.com> (raw)
In-Reply-To: <AM9PR09MB499564F2498A2C07EF2E6D05A1599@AM9PR09MB4995.eurprd09.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Hi Yaron

Maybe the caching takes PCI bandwidth?

Matan


From: Yaron Illouz <yaroni@radcom.com>
Sent: Wednesday, January 19, 2022 4:27 PM
To: dev@dpdk.org
Cc: Matan Azrad <matan@nvidia.com>
Subject: mellanox connect x 5 drops when cache full

External email: Use caution opening links or attachments

Hi

I am using multiqueue with RSS to read from MT27800 Family [ConnectX-5] 1017

My application receive traffic, and write some data to disk. As a result I/O write is cached in linux memory.
When the server memory is completely cache ( I know it is still available) I start seeing drops at nic.
If I delete the data from disk every minute the cached memory is released to free and and no drops at nic.
How can I avoid the drops at nic?

        total        used        free      shared  buff/cache   available
Mem:           125G         77G        325M         29M         47G         47G
Swap:          8.0G        256K        8.0G


[-- Attachment #2: Type: text/html, Size: 4546 bytes --]

      reply	other threads:[~2022-01-20 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 14:27 Yaron Illouz
2022-01-20 12:58 ` Matan Azrad [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=BL1PR12MB53803F145BD0598DCEE9C618DF5A9@BL1PR12MB5380.namprd12.prod.outlook.com \
    --to=matan@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=yaroni@radcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).