From: Oleg <lego12239@yandex.ru>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nfqueue buf size for recv()
Date: Thu, 20 Apr 2017 11:45:56 +0300 [thread overview]
Message-ID: <20170420084555.GB26208@legohost> (raw)
In-Reply-To: <20170419214521.GD17294@breakpoint.cc>
On Wed, Apr 19, 2017 at 11:45:21PM +0200, Florian Westphal wrote:
> Oleg <lego12239@yandex.ru> wrote:
> > Can anybody tell me how can i determine a right buf size for recv()
> > in libnetfilter_queue program.
> >
> > http://www.netfilter.org/projects/libnetfilter_queue/doxygen/group__Queue.html#gae36aee5b74d0c88d2f8530e356f68b79
> >
> > tells nothing about this.
>
> I'd suggest a 80k buffer to be on safe side.
My computations give my 70k buffer, but 80k is also suitable.
Thanks.
--
Олег Неманов (Oleg Nemanov)
prev parent reply other threads:[~2017-04-20 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 16:50 nfqueue buf size for recv() Oleg
2017-04-19 21:45 ` Florian Westphal
2017-04-20 8:45 ` Oleg [this message]
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=20170420084555.GB26208@legohost \
--to=lego12239@yandex.ru \
--cc=fw@strlen.de \
--cc=netfilter-devel@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 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).