From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nftables 4/4] src: mnl: retry when we hit -ENOBUFS
Date: Tue, 13 Aug 2019 21:36:29 +0200 [thread overview]
Message-ID: <20190813193629.sypzwky5m6fhgy7d@breakpoint.cc> (raw)
In-Reply-To: <20190813193442.4egmzohinumixuth@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > diff --git a/src/mnl.c b/src/mnl.c
> > index 97a2e0765189..0c7a4c1fa63f 100644
> > --- a/src/mnl.c
> > +++ b/src/mnl.c
> > @@ -311,6 +311,7 @@ int mnl_batch_talk(struct netlink_ctx *ctx, struct list_head *err_list,
> > int ret, fd = mnl_socket_get_fd(nl), portid = mnl_socket_get_portid(nl);
> > uint32_t iov_len = nftnl_batch_iovec_len(ctx->batch);
> > char rcv_buf[MNL_SOCKET_BUFFER_SIZE];
> > + unsigned int enobuf_restarts = 0;
> > size_t avg_msg_size, batch_size;
> > const struct sockaddr_nl snl = {
> > .nl_family = AF_NETLINK
> > @@ -320,6 +321,7 @@ int mnl_batch_talk(struct netlink_ctx *ctx, struct list_head *err_list,
> > .tv_usec = 0
> > };
> > struct iovec iov[iov_len];
> > + unsigned int scale = 4;
> > struct msghdr msg = {};
> > fd_set readfds;
> >
> > @@ -327,9 +329,7 @@ int mnl_batch_talk(struct netlink_ctx *ctx, struct list_head *err_list,
> >
> > batch_size = mnl_nft_batch_to_msg(ctx, &msg, &snl, iov, iov_len);
> > avg_msg_size = div_round_up(batch_size, num_cmds);
> > -
> > - mnl_set_rcvbuffer(ctx->nft->nf_sock, num_cmds * avg_msg_size * 4);
>
> Leaving this in place does not harm, right? This would speed up things
> for x86_64.
ok, I can keep it.
> It looks like s390 allocates larger page there to accomodate each
> netlink event.
>
> All this probing and guess games could be fixed if there is a
> getsockopt() to fetch sk->sk_rmem_alloc, this is already exposed in
> netlink via /proc. Later :-)
How? The error occurs because sk_rmem_alloc is not large enough to
store all the netlink acks in the socket backlog.
next prev parent reply other threads:[~2019-08-13 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 18:44 [PATCH nftables 0/4] un-break nftables on big-endian arches Florian Westphal
2019-08-13 18:44 ` [PATCH nftables 1/4] src: fix jumps on bigendian arches Florian Westphal
2019-08-13 19:20 ` Pablo Neira Ayuso
2019-08-13 19:34 ` Florian Westphal
2019-08-13 19:35 ` Pablo Neira Ayuso
2019-08-13 18:44 ` [PATCH nftables 2/4] src: parser: fix parsing of chain priority and policy on bigendian Florian Westphal
2019-08-13 19:26 ` Pablo Neira Ayuso
2019-08-13 18:44 ` [PATCH nftables 3/4] src: mnl: fix setting rcvbuffer size Florian Westphal
2019-08-13 19:26 ` Pablo Neira Ayuso
2019-08-13 18:44 ` [PATCH nftables 4/4] src: mnl: retry when we hit -ENOBUFS Florian Westphal
2019-08-13 19:34 ` Pablo Neira Ayuso
2019-08-13 19:36 ` Florian Westphal [this message]
2019-08-13 19:39 ` Pablo Neira Ayuso
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=20190813193629.sypzwky5m6fhgy7d@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).