DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mohsin Shaikh <mohsinshaikh@niometrics.com>
To: dev@dpdk.org
Cc: akozyrev@mellanox.com
Subject: Re: [dpdk-dev] [Bug 440] net/mlx5: Read of "out_of_buffer" using fopen/fscanf/fclose causing TLB shootdowns due to mmap/munmap
Date: Thu, 9 Apr 2020 12:26:51 +0800	[thread overview]
Message-ID: <E993FFAF-3992-466A-B6C0-41DE745D0C42@niometrics.com> (raw)
In-Reply-To: <bug-440-272-PxGGXr8U9C@http.bugs.dpdk.org/>

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

Hi Alexander,

Thank you for your quick response. Please find attached the patch for bug 440. 

- Mohsin


[-- Attachment #2: Type: text/plain, Size: 1007 bytes --]



> On 9 Apr 2020, at 1:07 AM, bugzilla@dpdk.org wrote:
> 
> https://bugs.dpdk.org/show_bug.cgi?id=440
> 
> Alexander Kozyrev (akozyrev@mellanox.com) changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>     Ever confirmed|0                           |1
>             Status|UNCONFIRMED                 |CONFIRMED
>                 CC|                            |akozyrev@mellanox.com
> 
> --- Comment #1 from Alexander Kozyrev (akozyrev@mellanox.com) ---
> Hi Mohsin, thank you for the problem description and especially for the patch.
> Would you mind sending this patch to DPDK mailing list so we can integrate it?
> The patch looks really good to me. The only small thing I would like to change.
> Could you please use SCNu64 macro instead of "%lu" in the sscanf function?
>    sscanf(buf, "%" SCNu64, stat);
> 
> -- 
> You are receiving this mail because:
> You reported the bug.


       reply	other threads:[~2020-04-09  4:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-440-272@http.bugs.dpdk.org/>
     [not found] ` <bug-440-272-PxGGXr8U9C@http.bugs.dpdk.org/>
2020-04-09  4:26   ` Mohsin Shaikh [this message]
2020-04-09  4:44     ` Mohsin Shaikh

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=E993FFAF-3992-466A-B6C0-41DE745D0C42@niometrics.com \
    --to=mohsinshaikh@niometrics.com \
    --cc=akozyrev@mellanox.com \
    --cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).