mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "MacCana, Mike" <mike.maccana@credit-suisse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Seeing TCP socket options (nodelay, cork, etc) in Linux procfs or elsewhere?
Date: Mon, 15 Mar 2010 17:20:31 +0100	[thread overview]
Message-ID: <1268670031.3154.35.camel@edumazet-laptop> (raw)
In-Reply-To: <5608FA8A997F1A46B7E985494F8478DD07930AF1@ELON17P32003A.csfb.cs-group.com>

Le lundi 15 mars 2010 à 15:49 +0000, MacCana, Mike a écrit :
> Hi kernel folks,
>  
> I was wondering if there was a standard location to see TCP socket
> options (eg, nodelay, cork, etc), perhaps via procfs or some other
> means? I'd like to check whether arbitrary apps (for which I don't have
> code) are using particular TCP options. 
>  
> Wandering round /proc/net hasn't turned up anything yet, and after a
> quick:
> socket.setsockopt(0, 1, 1)
> to enable NODELAY I can't see any obvious difference in procfs or
> netstat output (where other Unixes seem to put this info). hat's the
> best way to see TCP options on sockets created by others' code?
> 

There is limited support given by ss command (part of iproute2) :

ss -emoi

ESTAB       0      0                                55.225.18.5:4900
55.225.18.5:50000    uid:501 ino:135421 sk:c3b405c0
	 mem:(r0,w0,f4096,t0) ts bic wscale:6,6 rto:201 rtt:1/0.5 ato:40 cwnd:3
send 393.2Mbps rcv_space:32768


But CORK flag is not exported yet (its usually a volatile flag, at least
with Apache server)




  reply	other threads:[~2010-03-15 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 15:49 MacCana, Mike
2010-03-15 16:20 ` Eric Dumazet [this message]
2010-03-15 16:37   ` MacCana, Mike
2010-03-15 16:40     ` MacCana, Mike
2010-03-16 18:24       ` MacCana, Mike

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=1268670031.3154.35.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.maccana@credit-suisse.com \
    /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

all inboxes | Powered by JetHome®