public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Rony Ross <rony.ross@gmail.com>
Subject: Re: Supporting new Windows UDP offload features
Date: Mon, 2 May 2022 19:54:58 +0200	[thread overview]
Message-ID: <YnAa8sGkWeVIdHnt@calimero.vinschen.de> (raw)
In-Reply-To: <CAMnBwJRfAxbFiz4LSdX4m2P_gKcMbzS=GYfUHLTiyUdMqi2Jfg@mail.gmail.com>

On May  2 17:11, Rony Ross wrote:
> Hello,
> 
> Starting from Windows 10 version 2004, Windows supports UDP
> segmentation offload and UDP receive coalescing as described in
> https://docs.microsoft.com/en-us/windows-hardware/drivers/network/udp-segmentation-offload-uso-#ndis-interface-changes
> and in https://docs.microsoft.com/en-us/windows/win32/winsock/ipproto-udp-socket-options
> It seems that in order to support UDP segmentaion offload and UDP
> receive coalescing, cygwin needs to add support for UDP_SEND_MSG_SIZE
> and UDP_RECV_MAX_COALESCED_SIZE socket options for IPPROTO_UDP
> 
> Could you please add it?

Reading about those, it looks like they might be drop-in solutions
to implement the Linux UDP_SEGMENT and UDP_GRO socket options.
Knowing Windows however, I'm sure there's a twist somewhere...

> If so, could you please estimate when it will be available?

In the hopes they work the same way, I can make the UDP_SEGMENT and
UDP_GRO socket options available in the next major Cygwin version.

Availability, probably at some point late this year. Or later.
We're not at a point where this is safe to say.

However, test versions can be made available rather soon, I think.


Corinna

  parent reply	other threads:[~2022-05-02 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 14:11 Rony Ross
2022-05-02 17:51 ` Brian Inglis
2022-05-02 17:54 ` Corinna Vinschen [this message]
2022-05-24  5:50 rony.ross
2022-09-19  8:23 ` Rony Ross
2022-09-19 19:27   ` Ken Brown

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=YnAa8sGkWeVIdHnt@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=rony.ross@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).