From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: net-next closing, README
Date: Wed, 7 Dec 2016 19:20:18 -0800 [thread overview]
Message-ID: <20161207192018.4b1d1b2a@xeon-e3> (raw)
In-Reply-To: <20161207191345.6e765651@xeon-e3>
On Wed, 7 Dec 2016 19:13:45 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> On Wed, 07 Dec 2016 16:28:45 -0500 (EST)
> David Miller <davem@davemloft.net> wrote:
>
> > The merge window is about to open soon, and next week I will be
> > having sporadic internet access while travelling around, therefore
> > I am closing net-next up tonight.
> >
> > Therefore, please do not submit any new features or cleanups for
> > net-next. Bug fixes for problems introduced in net-next are fine,
> > however.
> >
> > Thank you.
>
> I have a couple of patches that I would like to get into net-next, but
> it is not critical. They replace the hardcoded workarounds with code
> that negotiates values with the host. Would these be acceptable?
> Sorry for the delay but needed to test on oldest supported version
> to ensure negotiation worked.
Never mind, although the changes work on older versions of Windows Server,
the performance would be worse. Basically old servers don't do UDP checksum
offload but still are capable of handling TCP. Let me work up a better
solution that handles both cases.
next prev parent reply other threads:[~2016-12-08 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 21:28 net-next closing, README David Miller
2016-12-08 3:13 ` Stephen Hemminger
2016-12-08 3:20 ` Stephen Hemminger [this message]
2016-12-08 22:02 ` Timur Tabi
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=20161207192018.4b1d1b2a@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--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).