From: Cong Wang <amwang@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Thomas Graf <tgraf@suug.ch>
Subject: Re: [Patch iproute2] add quickack option to ip route
Date: Tue, 16 Jul 2013 10:29:32 +0800 [thread overview]
Message-ID: <1373941772.25489.7.camel@cr0> (raw)
In-Reply-To: <20130619181722.50b2d7b7@nehalam.linuxnetplumber.net>
On Wed, 2013-06-19 at 18:17 -0700, Stephen Hemminger wrote:
> On Sat, 15 Jun 2013 09:39:19 +0800
> Cong Wang <amwang@redhat.com> wrote:
>
> > From: Cong Wang <amwang@redhat.com>
> >
> > This patch adds quickack option to enable/disable TCP quick ack
> > mode for per-route.
> >
> > Cc: Stephen Hemminger <stephen@networkplumber.org>
> > Cc: "David S. Miller" <davem@davemloft.net>
> > Cc: Thomas Graf <tgraf@suug.ch>
> > Signed-off-by: Cong Wang <amwang@redhat.com>
> >
>
> I am still waiting until RTAX_QUICKACK is accepted into net-next to apply to net-next-3.10 branch
> of iproute
>
>
The kernel patch was already merged into Linus tree, so could you apply
it now? Do I need to resend it?
Thanks!
next prev parent reply other threads:[~2013-07-16 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 1:39 [Patch net-next v3] tcp: introduce a per-route knob for quick ack Cong Wang
2013-06-15 1:39 ` [Patch iproute2] add quickack option to ip route Cong Wang
2013-06-20 1:17 ` Stephen Hemminger
2013-07-16 2:29 ` Cong Wang [this message]
2013-06-20 6:07 ` [Patch net-next v3] tcp: introduce a per-route knob for quick ack David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-06-13 6:24 [Patch net-next v2] " Cong Wang
2013-06-13 6:24 ` [Patch iproute2] add quickack option to ip route Cong Wang
2013-06-12 9:55 [Patch net-next] tcp: introduce a per-route knob for quick ack Cong Wang
2013-06-12 9:55 ` [Patch iproute2] add quickack option to ip route Cong Wang
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=1373941772.25489.7.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.