linux-newbie.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ashoka K <ashok.vinu@gmail.com>
Cc: linux-newbie@vger.kernel.org,
	Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: Any issue to be considered if ethernet send buffer is modified
Date: Fri, 11 Oct 2013 11:51:23 +0200	[thread overview]
Message-ID: <20131011095123.GB6983@linutronix.de> (raw)
In-Reply-To: <CALJd4cb9aZF=jzbYiAf518KW-hS+QR4u0JDHefmR5Q4DipOuPw@mail.gmail.com>

* Ashoka K | 2013-08-30 13:51:14 [+0530]:

>Hi,
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?

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.

>AK

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@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

      reply	other threads:[~2013-10-11  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30  8:21 Any issue to be considered if ethernet send buffer is modified Ashoka K
2013-10-11  9:51 ` Sebastian Andrzej Siewior [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=20131011095123.GB6983@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=ashok.vinu@gmail.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).