From: Jiri Benc <jbenc@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: pablo@netfilter.org, jhs@mojatatu.com, tgraf@suug.ch,
netdev@vger.kernel.org
Subject: Re: [PATCH net] netlink: fix netlink_ack with large messages
Date: Wed, 13 Nov 2013 12:25:04 +0100 [thread overview]
Message-ID: <20131113122504.0ddcbf89@griffin> (raw)
In-Reply-To: <20131112.143515.1092879587357986857.davem@davemloft.net>
On Tue, 12 Nov 2013 14:35:15 -0500 (EST), David Miller wrote:
> > Do you think capping at NLMSG_GOODSIZE would be too low? The allocation
> > won't fit into one page with NLMSG_GOODSIZE but I doubt we can go lower
> > than that. Alternatively, we can do some math to fully use the two
> > pages, like
> > NLMSG_GOODSIZE + min(PAGE_SIZE, 8192UL) - NLMSG_HDRLEN - NLMSG_ALIGN(sizeof(struct nlmsgerr))
> > (which I'm not sure is worth it).
>
> I don't think this is the way to go.
>
> I think since existing apps expect the whole message, we have to
> provide it.
>
> We should add a new socket option so that applications can ask that
> messages not be quoted in ACKs, as I've stated a few times already in
> this thread.
I completely agree with this, sorry for not being clear. I just
understood from the thread that the way to go is to do both, in order
to not generate too large ACKs for the _new_ code (i.e. for the
messages that were not plausible before "netlink: allow large data
transfers from user-space"). I don't know what the "too large" should
be, though, hence the question.
But then, if we don't do any capping, the only outcome of a failed
allocation is the ACK won't be sent and it's clearly stated that
netlink does not provide reliability. Works for me.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2013-11-13 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 18:57 [PATCH net] netlink: fix netlink_ack with large messages Jiri Benc
2013-11-08 20:07 ` David Miller
2013-11-09 0:04 ` Thomas Graf
2013-11-09 5:00 ` David Miller
2013-11-09 13:43 ` Jamal Hadi Salim
2013-11-09 18:03 ` Pablo Neira Ayuso
2013-11-12 15:29 ` Jiri Benc
2013-11-12 19:35 ` David Miller
2013-11-13 11:25 ` Jiri Benc [this message]
2013-11-13 20:43 ` David Miller
2013-11-09 19:27 ` David Miller
2013-11-09 19:49 ` 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=20131113122504.0ddcbf89@griffin \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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.