Discussion:
Any issue to be considered if ethernet send buffer is modified
Ashoka K
2013-08-30 08:21:14 UTC
Permalink
Hi,

I use embedded system with 2.6.33, Preempt patch. To reduce the
latency of sending data by our application, the ethernet send buffer
is modified with setsockopt().

Before modification the send buffer size by default was shown as 16384 bytes.
But on proc system value shown is different, both default and max are same:
/proc/sys/net/core/wmem_default = 108544

Eventhough the above value is not modified, why the default is shown
as 16384 instead 108544. Did kernel change these values during sending
traffic ?

If send buffer is set by setsockopt(), is this value modified by
kernel during run time?

AK
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Sebastian Andrzej Siewior
2013-10-11 09:51:23 UTC
Permalink
Post by Ashoka K
Hi,
Hi,
Post by Ashoka K
I use embedded system with 2.6.33, Preempt patch. To reduce the
latency of sending data by our application, the ethernet send buffer
is modified with setsockopt().
Before modification the send buffer size by default was shown as 16384 bytes.
/proc/sys/net/core/wmem_default = 108544
Eventhough the above value is not modified, why the default is shown
as 16384 instead 108544. Did kernel change these values during sending
traffic ?
If send buffer is set by setsockopt(), is this value modified by
kernel during run time?
Try to grep for sysctl_wmem_default. Atleast on v3.10 this value is
initialized at compile time and only updated via sysctl and not by the
kernel.
Post by Ashoka K
AK
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Loading...