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" :) -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
