yet another option would be to setup point-to-point ethernet device
(^^) via tun/tap drivers. you can have a userland program receiving
data from the said device, and then use whatever options you want
there.
anupam
On Tue, May 31, 2011 at 8:11 AM, Anupam Kapoor wrote:
> yup, that's what i also
On Tue, May 31, 2011 at 09:41, Anupam Kapoor wrote:
> yup, that's what i also think. is it possible that nagle+delayed-ack
> is causing the perceived slow-down ?
could be, but have you tried to switch and use various congestion
control ? check /proc/sys/net/ipv4/tcp_congestion_control and here ar
yup, that's what i also think. is it possible that nagle+delayed-ack
is causing the perceived slow-down ?
anupam
On Tue, May 31, 2011 at 6:03 AM, Peter Teoh wrote:
> frankly it is not wise to disable nagle, and the solution i proposed
> (using netfilter extension) is really too tedious - the add
frankly it is not wise to disable nagle, and the solution i proposed
(using netfilter extension) is really too tedious - the added overhead
may slow down the processing, even though disabling nagle aims to
improve latencies. but modern network card is so fast, that the
bottleneck is not at the ne
>
>
> --
> Regards,
> Peter Teoh
>
>
>
Thank you very much Peter.
Regards,
Kashyap
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Mon, May 30, 2011 at 4:07 PM, C K Kashyap wrote:
>> Yes, TCP_NODELAY is a socket option:
>>
>> Going back to the kernel source:
>>
>> include/linux/tcp.h:
>>
>> #define TCP_NODELAY 1 /* Turn off Nagle's algorithm. */
>>
>> and this:
>>
>> u8 nonagle : 4,/* Disab
>
> Yes, TCP_NODELAY is a socket option:
>
> Going back to the kernel source:
>
> include/linux/tcp.h:
>
> #define TCP_NODELAY 1 /* Turn off Nagle's algorithm. */
>
> and this:
>
> u8 nonagle : 4,/* Disable Nagle algorithm? */
>
> and looking into the ke
On Mon, May 30, 2011 at 12:47 PM, C K Kashyap wrote:
>
>
> On Mon, May 30, 2011 at 9:53 AM, Anupam Kapoor
> wrote:
>>
>> is tcp_nodelay not an option ?
>>
>
> Is this a socket option or is there a system wide setting for tcp_nodelay?
Yes, TCP_NODELAY is a socket option:
Going back to the kernel
On Mon, May 30, 2011 at 9:53 AM, Anupam Kapoor wrote:
> is tcp_nodelay not an option ?
>
>
Is this a socket option or is there a system wide setting for tcp_nodelay?
Regards,
Kashyap
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http:/
is tcp_nodelay not an option ?
anupam
On Mon, May 30, 2011 at 9:21 AM, C K Kashyap wrote:
>
>
> On Mon, May 30, 2011 at 9:18 AM, Anupam Kapoor
> wrote:
>>
>> afaik, it disables tcp-prequeue nothing to do with nagle anyways.
>> also, doing this might have marginal benefits if anything at all due
On Mon, May 30, 2011 at 9:18 AM, Anupam Kapoor wrote:
> afaik, it disables tcp-prequeue nothing to do with nagle anyways.
> also, doing this might have marginal benefits if anything at all due
> to most overhead being specific to context switching than anything
> else.
>
> Thanks Anupam ... can yo
afaik, it disables tcp-prequeue nothing to do with nagle anyways.
also, doing this might have marginal benefits if anything at all due
to most overhead being specific to context switching than anything
else.
anupam
On Sun, May 29, 2011 at 11:04 PM, C K Kashyap wrote:
> Hi,
> Is setting net.ipv4.
Hi,
Is setting *net.ipv4.tcp_low_latency to 1 the right way of disabling nagle's
algorithm?*
*Regards,*
*Kashyap*
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
13 matches
Mail list logo
