DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Fengnan Chang <changfengnan@bytedance.com>, <david.marchand@redhat.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v3] eal: fix prompt info when remap_segment failed
Date: Tue, 4 Jul 2023 13:43:25 +0100	[thread overview]
Message-ID: <bc2cbbe6-4bf8-98d4-be5f-1b171bee2a14@intel.com> (raw)
In-Reply-To: <20230704121751.92253-1-changfengnan@bytedance.com>

On 7/4/2023 1:17 PM, Fengnan Chang wrote:
> When there is not enough space to memsegs, we should prompt
> which configuration should be modified instead of printing
> some numbers.
> 
> Signed-off-by: Fengnan Chang <changfengnan@bytedance.com>
> ---

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

-- 
Thanks,
Anatoly


  reply	other threads:[~2023-07-04 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 12:17 Fengnan Chang
2023-07-04 12:43 ` Burakov, Anatoly [this message]
2023-07-05  1:33 ` fengchengwen
2023-07-06 14:16   ` Thomas Monjalon

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=bc2cbbe6-4bf8-98d4-be5f-1b171bee2a14@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=changfengnan@bytedance.com \
    --cc=david.marchand@redhat.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).