On 12-Aug-19 10:49 AM, David Marchand wrote:
On Mon, Aug 12, 2019 at 11:43 AM Burakov, Anatoly
wrote:
On 08-Aug-19 8:31 AM, Thomas Monjalon wrote:
I would suggest to restrict the change to Arm only with an ifdef,
in order to limit the risk for this release.
We can think about a dynamic hugepag
12/08/2019 11:49, David Marchand:
> On Mon, Aug 12, 2019 at 11:43 AM Burakov, Anatoly
> wrote:
> > On 08-Aug-19 8:31 AM, Thomas Monjalon wrote:
> > > I would suggest to restrict the change to Arm only with an ifdef,
> > > in order to limit the risk for this release.
> > > We can think about a dyna
On Mon, Aug 12, 2019 at 11:43 AM Burakov, Anatoly
wrote:
> On 08-Aug-19 8:31 AM, Thomas Monjalon wrote:
> > I would suggest to restrict the change to Arm only with an ifdef,
> > in order to limit the risk for this release.
> > We can think about a dynamic hugepage scan in the next release.
> >
>
>
On 08-Aug-19 8:31 AM, Thomas Monjalon wrote:
07/08/2019 15:28, Hemant Agrawal:
HI Thomas,
DPDK currently is supporting maximum 3 hugepage, sizes whereas
system can support more than this e.g.
64K, 2M, 32M and 1G.
You can mention ARM platform here, and that this issue starts with
kernel 5.2 (
On 07-Aug-19 2:28 PM, Hemant Agrawal wrote:
HI Thomas,
DPDK currently is supporting maximum 3 hugepage, sizes whereas
system can support more than this e.g.
64K, 2M, 32M and 1G.
You can mention ARM platform here, and that this issue starts with
kernel 5.2 (and I would try to mention this in t
Hello,
On Thu, Aug 08, 2019 at 10:37:20AM +, Hemant Agrawal wrote:
> Hi David,
>
> > > VPP usages in-memory option. So, VPP on ARM with kernel 5.2 wont' work
> > without this patch.
> > >
> >
> > I have been looking at the changes in the linux kernel.
> > Can you pinpoint at the commit that
On Thu, Aug 8, 2019 at 2:29 PM Steve Capper wrote:
>
> Hello,
>
> On Thu, Aug 08, 2019 at 10:37:20AM +, Hemant Agrawal wrote:
> > Hi David,
> >
> > > > VPP usages in-memory option. So, VPP on ARM with kernel 5.2 wont' work
> > > without this patch.
> > > >
> > >
> > > I have been looking at th
Hi David,
> > VPP usages in-memory option. So, VPP on ARM with kernel 5.2 wont' work
> without this patch.
> >
>
> I have been looking at the changes in the linux kernel.
> Can you pinpoint at the commit that changed this in 5.2?
>
> I can see a change in the code, but in 5.0, or maybe something
On Thu, Aug 8, 2019 at 11:00 AM Gagandeep Singh wrote:
>
> > >HI Thomas,
> > > > > > DPDK currently is supporting maximum 3 hugepage, sizes whereas
> > > > > > system can support more than this e.g.
> > > > > > 64K, 2M, 32M and 1G.
> > > > >
> > > > > You can mention ARM platform here, and that th
> >HI Thomas,
> > > > > DPDK currently is supporting maximum 3 hugepage, sizes whereas
> > > > > system can support more than this e.g.
> > > > > 64K, 2M, 32M and 1G.
> > > >
> > > > You can mention ARM platform here, and that this issue starts with
> > > > kernel 5.2 (and I would try to mention th
On Wed, Aug 7, 2019 at 3:28 PM Hemant Agrawal wrote:
>
> HI Thomas,
>
> > > > DPDK currently is supporting maximum 3 hugepage, sizes whereas
> > > > system can support more than this e.g.
> > > > 64K, 2M, 32M and 1G.
> > >
> > > You can mention ARM platform here, and that this issue starts with
>
07/08/2019 15:28, Hemant Agrawal:
> HI Thomas,
>
> > > > DPDK currently is supporting maximum 3 hugepage, sizes whereas
> > > > system can support more than this e.g.
> > > > 64K, 2M, 32M and 1G.
> > >
> > > You can mention ARM platform here, and that this issue starts with
> > > kernel 5.2 (and I
On Wed, 7 Aug 2019 15:42:04 +0530
Gagandeep Singh wrote:
> DPDK currently is supporting maximum 3 hugepage,
> sizes whereas system can support more than this e.g.
> 64K, 2M, 32M and 1G.
>
> Having these four hugepage sizes available to use by DPDK,
> which is valid in case of '--in-memory' EAL
> Hi Thomas,
>
> > 07/08/2019 14:00, David Marchand:
> > > On Wed, Aug 7, 2019 at 12:26 PM Gagandeep Singh
> > wrote:
> > > >
> > > > DPDK currently is supporting maximum 3 hugepage, sizes whereas
> > > > system can support more than this e.g.
> > > > 64K, 2M, 32M and 1G.
> > >
> > > You can m
HI Thomas,
> > > DPDK currently is supporting maximum 3 hugepage, sizes whereas
> > > system can support more than this e.g.
> > > 64K, 2M, 32M and 1G.
> >
> > You can mention ARM platform here, and that this issue starts with
> > kernel 5.2 (and I would try to mention this in the title as well).
Hi Thomas,
> 07/08/2019 14:00, David Marchand:
> > On Wed, Aug 7, 2019 at 12:26 PM Gagandeep Singh
> wrote:
> > >
> > > DPDK currently is supporting maximum 3 hugepage,
> > > sizes whereas system can support more than this e.g.
> > > 64K, 2M, 32M and 1G.
> >
> > You can mention ARM platform here,
>
> On Wed, Aug 7, 2019 at 12:26 PM Gagandeep Singh wrote:
> >
> > DPDK currently is supporting maximum 3 hugepage,
> > sizes whereas system can support more than this e.g.
> > 64K, 2M, 32M and 1G.
>
> You can mention ARM platform here, and that this issue starts with
> kernel 5.2 (and I would
07/08/2019 14:00, David Marchand:
> On Wed, Aug 7, 2019 at 12:26 PM Gagandeep Singh wrote:
> >
> > DPDK currently is supporting maximum 3 hugepage,
> > sizes whereas system can support more than this e.g.
> > 64K, 2M, 32M and 1G.
>
> You can mention ARM platform here, and that this issue starts w
On Wed, Aug 7, 2019 at 12:26 PM Gagandeep Singh wrote:
>
> DPDK currently is supporting maximum 3 hugepage,
> sizes whereas system can support more than this e.g.
> 64K, 2M, 32M and 1G.
You can mention ARM platform here, and that this issue starts with
kernel 5.2 (and I would try to mention this
DPDK currently is supporting maximum 3 hugepage,
sizes whereas system can support more than this e.g.
64K, 2M, 32M and 1G.
Having these four hugepage sizes available to use by DPDK,
which is valid in case of '--in-memory' EAL option or
using 4 separate mount points for each hugepage size;
hugepage
20 matches
Mail list logo
