DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>
Cc: "mb@smartsharesystems.com" <mb@smartsharesystems.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"ktraynor@redhat.com" <ktraynor@redhat.com>,
	"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
	"aconole@redhat.com" <aconole@redhat.com>,
	"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
	dev@dpdk.org
Subject: Re: [PATCH v2] config/x86: config support for AMD EPYC processors
Date: Tue, 13 Feb 2024 15:28:00 +0100	[thread overview]
Message-ID: <5354841.kQq0lBPeGt@thomas> (raw)
In-Reply-To: <7ea559e6826943d8b515ab0ca56a38b8@huawei.com>

02/01/2024 19:18, Konstantin Ananyev:
> 
> > On x86 platforms, max lcores are limited to 128 by default.
> > 
> > On AMD EPYC processors, this limit was adjusted for native
> > builds in the previous patch.
> > https://patches.dpdk.org/project/dpdk/patch/
> > 20230925151027.558546-1-sivaprasad.tummala@amd.com/
> > 
> > As agreed earlier in mailing list, this patch adjusts the limit
> > for specific AMD EPYC target/cross builds.
> > 
> > Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
> 
> Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>

Applied, thanks.



      reply	other threads:[~2024-02-13 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  7:10 [PATCH] " Sivaprasad Tummala
2023-12-20  7:27 ` Morten Brørup
2023-12-20  9:22   ` Tummala, Sivaprasad
2023-12-21  5:11 ` [PATCH v2] " Sivaprasad Tummala
2024-01-02 18:18   ` Konstantin Ananyev
2024-02-13 14:28     ` Thomas Monjalon [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=5354841.kQq0lBPeGt@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=konstantin.ananyev@huawei.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mb@smartsharesystems.com \
    --cc=sivaprasad.tummala@amd.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).