public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: Re: Supporting new Windows UDP offload features
Date: Mon, 2 May 2022 11:51:17 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-05-02 08:11, Rony Ross wrote:
> Starting from Windows 10 version 2004, Windows supports UDP
> segmentation offload and UDP receive coalescing as described in
> and in
> It seems that in order to support UDP segmentaion offload and UDP
> receive coalescing, cygwin needs to add support for UDP_SEND_MSG_SIZE
> Could you please add it? If so, could you please estimate when it will
> be available?

Cygwin is an all-volunteer non-commercial open source POSIX/Linux 
emulation project, typically driven by developers' needs and interests, 
sometimes offering patchsets to add or enable features previously 
available in BSD flavours.

If you are not a developer capable of doing so, you will have to wait 
and see if any developer is inspired by your post, and has the free time 
to work on it.

You might want to help this along by expanding on some description of 
use cases, impacts, advantages, benefits, downsides, Unix parameters and 
implementations to be supported for emulation, Unix and Windows 
configuration of features, and availability on NICs, of those network 

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-05-02 17:51 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 [this message]
2022-05-02 17:54 ` Corinna Vinschen
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).