From: Marcel Holtmann <marcel@holtmann.org>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: padovan@profusion.mobi, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/3] Zero-copy L2CAP ERTM & streaming reassembly
Date: Tue, 19 Jul 2011 00:43:15 +0200 [thread overview]
Message-ID: <1311028996.21109.168.camel@aeonflux> (raw)
In-Reply-To: <alpine.DEB.2.02.1107181458360.8933@mathewm-linux>
Hi Mat,
> >>> This patch series changes SDU reassembly to link together PDU skbs
> >>> using a frag list instead of copying all data bytes to a single,
> >>> linear skb. The reduction in overhead is especially helpful with high
> >>> speed AMP links.
> >
> > I have not looked at these at all, but one thing that came up in a
> > discussion between Johan and myself with OBEX zero-copy was that we like
> > to also see MSG_MORE support for L2CAP and RFCOMM sockets. Something to
> > keep in mind ;)
>
> Noted! It would be nice to build up OBEX packets in the kernel,
> rather than having to assemble entire packets in an application
> buffer.
hence the request for MSG_MORE support. That would allow us to build
frames properly. Could also become a pretty nice enhancement for A2DP.
Regards
Marcel
prev parent reply other threads:[~2011-07-18 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 17:58 [PATCH 0/3] Zero-copy L2CAP ERTM & streaming reassembly Mat Martineau
2011-07-13 17:58 ` [PATCH 1/3] Bluetooth: Linearize skbs for use in BNEP, CMTP, HIDP, and RFCOMM Mat Martineau
2011-07-13 17:58 ` [PATCH 2/3] Bluetooth: Handle fragmented skbs in bt_sock_stream_recvmsg() Mat Martineau
2011-07-22 16:43 ` Gustavo Padovan
2011-07-22 19:20 ` Mat Martineau
2011-07-13 17:58 ` [PATCH 3/3] Bluetooth: Perform L2CAP SDU reassembly without copying data Mat Martineau
2011-07-22 16:46 ` Gustavo Padovan
2011-07-18 20:02 ` [PATCH 0/3] Zero-copy L2CAP ERTM & streaming reassembly Mat Martineau
2011-07-18 20:33 ` Marcel Holtmann
2011-07-18 22:18 ` Mat Martineau
2011-07-18 22:43 ` Marcel Holtmann [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=1311028996.21109.168.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.org \
--cc=padovan@profusion.mobi \
/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