netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Quetchenbach <virtualphtn@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, lachlan.andrew@gmail.com
Subject: Re: [PATCH][BUG] tcp: advertise MSS requested by user
Date: Fri, 29 Aug 2008 09:48:03 -0700	[thread overview]
Message-ID: <48B82843.4090707@gmail.com> (raw)
In-Reply-To: <200808281250.35006.denys@visp.net.lb>

Best I can tell, my mailer ate this reply, so apologies if you get it twice.

>> Thanks for your patch, I'll mull over this and put in the fix
>> once I understand exactly how this got broken.

David, thanks a lot for looking into this. It will be really helpful for
our TCP benchmarking work.

> I am using, just i workaround this over iptables MSS option. You feel 
> discomfort, but most people start googling and see this trick with iptables, 
> and they use it.

In my case I don't think the iptables workaround is the right solution.
I'm working on a traffic generator (tmix, from the University of North
Carolina), that starts many simultaneous flows between two endpoints,
based on a set of "connection vectors" derived from a tcpdump. The MSS
for each flow is specified in the connection vector file on a per-flow
basis. So it's not so simple as clamping the MSS to the path MTU or
setting it based on some simple criteria like destination or port
number. I'm sure I could hack something together using iptables to
approximate what I want to do, but it seems like a bit of a mess to me.

I'm not that familiar with iptables so please correct me if I'm wrong.

Thanks
-Tom


  reply	other threads:[~2008-08-29 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 18:11 [PATCH][BUG] tcp: advertise MSS requested by user Tom Quetchenbach
2008-08-28  9:46 ` David Miller
2008-08-28  9:50   ` Denys Fedoryshchenko
2008-08-29 16:48     ` Tom Quetchenbach [this message]
2008-08-29 16:57       ` Denys Fedoryshchenko
2008-09-21  7:22 ` David Miller
2009-06-13 10:12   ` Willy Tarreau

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=48B82843.4090707@gmail.com \
    --to=virtualphtn@gmail.com \
    --cc=davem@davemloft.net \
    --cc=denys@visp.net.lb \
    --cc=lachlan.andrew@gmail.com \
    --cc=netdev@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 NNTP newsgroup(s).