From: Eric Dumazet <eric.dumazet@gmail.com>
To: Roy Marples <roy@marples.name>
Cc: netdev@vger.kernel.org
Subject: Re: recv(2), MSG_TRUNK and kernels older than 2.6.22
Date: Tue, 20 Jul 2010 11:24:33 +0200 [thread overview]
Message-ID: <1279617873.2498.13.camel@edumazet-laptop> (raw)
In-Reply-To: <4C45678A.4080408@marples.name>
Le mardi 20 juillet 2010 à 10:08 +0100, Roy Marples a écrit :
> On 20/07/2010 09:54, Eric Dumazet wrote:
> > Is it for the dhcpcd problem we talk about few week ago, disturbed by
> > new 64bit stats ?
>
> Yes
>
> >
> > Why do you want to have a fixed size of 256 bytes ?
> >
> > Using 8192 bytes on stack would avoid MSG_TRUNK mess.
>
> Yes it would, but that doesn't answer my question :)
Your question might be wrong ? :=)
> I would like to use a buffer big enough, but not a whole 8k in size.
> dhcpcd has quite a small runtime and I'd like to keep it that way.
8192 bytes on stack is too much for you ?
Then you should automatically resize your buffer, and not using
MSG_TRUNK at all (there is no guarantee the information you need will be
part of the truncated part)
next prev parent reply other threads:[~2010-07-20 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 8:26 recv(2), MSG_TRUNK and kernels older than 2.6.22 Roy Marples
2010-07-20 8:54 ` Eric Dumazet
2010-07-20 9:08 ` Roy Marples
2010-07-20 9:24 ` Eric Dumazet [this message]
2010-07-20 10:02 ` Eric Dumazet
2010-07-20 10:04 ` Roy Marples
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=1279617873.2498.13.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roy@marples.name \
/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