[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] MSG_MORE flag for send
From: |
Marc CHALAND |
Subject: |
Re: [lwip-devel] MSG_MORE flag for send |
Date: |
Mon, 29 Oct 2007 09:53:04 +0100 |
2007/10/28, Frédéric BERNON <address@hidden>:
> Without adding a new parameter, since the existing "copy" parameter seems to
> be forwarded from sockets.c to tcp_out.c (in tcp_enqueue), why don't use it?
> We can rename it apiflags - or something else - (since flags is usein
> tcp_enqueue like "tcp flags"). I don't have study all case, but msg_more is
> an option "per 'write' call", like the "copy" option.
This was my first idea. I didn't want to disturb eventual special use
of this byte ?
However, this require change of tcp_write and so on functions...
Marc
- [lwip-devel] MSG_MORE flag for send, Marc CHALAND, 2007/10/26
- Re: [lwip-devel] MSG_MORE flag for send, Simon Goldschmidt, 2007/10/27
- Re: [lwip-devel] MSG_MORE flag for send, Jonathan Larmour, 2007/10/27
- Re: [lwip-devel] MSG_MORE flag for send, Simon Goldschmidt, 2007/10/27
- Re: [lwip-devel] MSG_MORE flag for send, Jonathan Larmour, 2007/10/27
- Re: [lwip-devel] MSG_MORE flag for send, Frédéric BERNON, 2007/10/28
- Re: [lwip-devel] MSG_MORE flag for send, Marc CHALAND, 2007/10/29
- Re: [lwip-devel] MSG_MORE flag for send,
Marc CHALAND <=
- RFC references (was Re: [lwip-devel] MSG_MORE flag for send), Jonathan Larmour, 2007/10/29
Re: [lwip-devel] MSG_MORE flag for send, Marc CHALAND, 2007/10/29
Re: [lwip-devel] MSG_MORE flag for send, Marc CHALAND, 2007/10/29