From: Alexei Starovoitov <ast@plumgrid.com>
To: Alex Gartrell <alexgartrell@gmail.com>, daniel@iogearbox.net
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Why return E2BIG from bpf map update?
Date: Mon, 20 Jul 2015 15:24:20 -0700 [thread overview]
Message-ID: <55AD7514.7040906@plumgrid.com> (raw)
In-Reply-To: <CALCkm3eCUYFOon6Gza4A8Ske8MS1rVFJJip_J9dWQp79ju8zBw@mail.gmail.com>
On 7/20/15 3:15 PM, Alex Gartrell wrote:
> The ship has probably sailed on this one, but it seems like ENOSPC
> makes more sense than E2BIG. Any chance of changing it so that poor
> ebpf library maintainers in the future don't have to wonder how their
> argument list got too big?
sorry, too late.
It's in tests and even document in bpf manpage:
"E2BIG - indicates that the number of elements in the map reached the
max_entries limit specified at map creation time."
I read E2BIG as "too big" and not as "argument list is too long" :)
next prev parent reply other threads:[~2015-07-20 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 22:15 Why return E2BIG from bpf map update? Alex Gartrell
2015-07-20 22:24 ` Alexei Starovoitov [this message]
2015-07-21 9:40 ` Daniel Borkmann
2015-07-21 10:13 ` Alex Gartrell
2015-07-21 21:34 ` Alexei Starovoitov
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=55AD7514.7040906@plumgrid.com \
--to=ast@plumgrid.com \
--cc=alexgartrell@gmail.com \
--cc=daniel@iogearbox.net \
--cc=netdev@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.