All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@dpdk.org, Patrick Robb <probb@iol.unh.edu>,
	stuart.schacher@broadcom.com, farah.smith@broadcom.com,
	sbhosle@broadcom.com,  Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH] test: eal: update base-virtaddr parameter test
Date: Sat, 22 Jul 2023 15:32:06 +0200	[thread overview]
Message-ID: <4150072.som1txNFv6@thomas> (raw)
In-Reply-To: <CACZ4nht0za=XrsmfNBaDH5=Nxdoza85MywN-g5k4ZPtFgXoExw@mail.gmail.com>

20/07/2023 16:07, Ajit Khaparde:
> On Thu, Jul 20, 2023 at 6:09 AM Aaron Conole <aconole@redhat.com> wrote:
> >
> > When 97435d7906 ("net/bnxt: update Truflow core") was applied, it introduced
> > a number of static variables.  These ended up filling the lower address space
> > enough that on some platforms, the min addr for heap address to start was
> > not within the range specified by base-virtaddr.  This is dependent on both
> > build and link time options.
> >
> > The simplest resolution is to just update the base virtaddr parameter to
> > move the rte config location.
> >
> > Reported-by: Patrick Robb <probb@iol.unh.edu>
> > Suggested-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> > Signed-off-by: Aaron Conole <aconole@redhat.com>
> ACK.
> I tested again and the test passed with this change. Thanks.

Applied, thanks.




      reply	other threads:[~2023-07-22 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 13:09 [PATCH] test: eal: update base-virtaddr parameter test Aaron Conole
2023-07-20 14:07 ` Ajit Khaparde
2023-07-22 13:32   ` 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=4150072.som1txNFv6@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=farah.smith@broadcom.com \
    --cc=probb@iol.unh.edu \
    --cc=sbhosle@broadcom.com \
    --cc=stuart.schacher@broadcom.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 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.