From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] btio: Adjust socket buffers to be at least as big as MTU
Date: Fri, 02 Mar 2012 16:33:50 -0800 [thread overview]
Message-ID: <1330734830.3392.132.camel@aeonflux> (raw)
In-Reply-To: <1328884361-3909-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
> Maybe could be done in kernel automatically as it could be considered
> broken in case of SOCK_SEQPACKET if socket buffer cannot hold a
> write/read of MTU size.
I have actually no idea what the right approach here is, but we should
handle this inside the kernel.
So should setting a too large MTU fail if the socket buffers are too
small? Or just we just adjust the socket buffers when a large MTU is
set? Any comments?
Regards
Marcel
next prev parent reply other threads:[~2012-03-03 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:32 [RFC] btio: Adjust socket buffers to be at least as big as MTU Luiz Augusto von Dentz
2012-03-01 16:25 ` Luiz Augusto von Dentz
2012-03-03 0:33 ` Marcel Holtmann [this message]
2012-03-05 8:57 ` Luiz Augusto von Dentz
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=1330734830.3392.132.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).