From: Magnus Karlsson <magnus.karlsson@gmail.com>
To: Dan Siemon <dan@coverfire.com>
Cc: "Björn Töpel" <bjorn@kernel.org>, Xdp <xdp-newbies@vger.kernel.org>
Subject: Re: Umem Questions
Date: Thu, 20 May 2021 08:14:34 +0200 [thread overview]
Message-ID: <CAJ8uoz023wsbt9mfa2V96kFgkQJiUqj-TG4etbyszWNh1u4qww@mail.gmail.com> (raw)
In-Reply-To: <da5422fe0fd031212d6e422177979354207aa609.camel@coverfire.com>
On Wed, May 19, 2021 at 11:09 PM Dan Siemon <dan@coverfire.com> wrote:
>
>
> > > 2) It looks like there is a limit of 2GB on the maximum Umem size?
> > > I've
> > > tried with and without huge pages. Is this fundamental? How hard
> > > would
> > > it be to increase this?
> >
> > This was news to me. Do you know where in the xdp_umem_reg code it
> > complains about this? I guess it is xsk_umem__create() that fails,
> > or?
> > The only limit I see from a basic inspection of the code is that the
> > number of packet buffers cannot be larger than a u32 (4G). But you
> > are
> > not close to that limit.
>
> Yes, the failure is in xsk_umem__create(). I don't know where
> specifically but there are a couple spots in kernel side of that which
> return ENOMEM which is the return value.
Can you issue a "ulimit -a" on your system and share the result? Just
to verify that there is no per process limit that kicks in.
next prev parent reply other threads:[~2021-05-20 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 14:34 Umem Questions Dan Siemon
2021-05-17 8:21 ` Magnus Karlsson
2021-05-19 21:09 ` Dan Siemon
2021-05-20 6:14 ` Magnus Karlsson [this message]
2021-05-20 12:40 ` Magnus Karlsson
2021-05-20 12:50 ` Magnus Karlsson
2021-05-21 18:17 ` Dan Siemon
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=CAJ8uoz023wsbt9mfa2V96kFgkQJiUqj-TG4etbyszWNh1u4qww@mail.gmail.com \
--to=magnus.karlsson@gmail.com \
--cc=bjorn@kernel.org \
--cc=dan@coverfire.com \
--cc=xdp-newbies@vger.kernel.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 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.