<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/Documentation/networking/msg_zerocopy.rst, branch v5.19</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v5.19</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v5.19'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2021-10-12T19:58:19+00:00</updated>
<entry>
<title>docs: use the lore redirector everywhere</title>
<updated>2021-10-12T19:58:19+00:00</updated>
<author>
<name>Thorsten Leemhuis</name>
<email>linux@leemhuis.info</email>
</author>
<published>2021-10-07T08:05:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=a9d85efb25fbc9d2356c221ff967f77ed9f71d59'/>
<id>urn:sha1:a9d85efb25fbc9d2356c221ff967f77ed9f71d59</id>
<content type='text'>
Change all links from using the lkml redirector to the lore redirector,
as the kernel.org admin recently indicated: we shouldn't be using
lkml.kernel.org anymore because the domain can create confusion, as it
indicates it is only valid for messages sent to the LKML; the convention
has been to use https://lore.kernel.org/r/msgid for this reason.

In this process also change three links from using http to https.

Link: https://lore.kernel.org/r/20211006170025.qw3glxvocczfuhar@meerkat.local
CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
CC: Ingo Molnar &lt;mingo@redhat.com&gt;
CC: Borislav Petkov &lt;bp@alien8.de&gt;
CC: Hu Haowen &lt;src.res@email.cn&gt;
CC: Alex Shi &lt;alexs@kernel.org&gt;
CC: Federico Vaga &lt;federico.vaga@vaga.pv.it&gt;
Signed-off-by: Thorsten Leemhuis &lt;linux@leemhuis.info&gt;
Reviewed-by: Konstantin Ryabitsev &lt;konstantin@linuxfoundation.org&gt;
Link: https://lore.kernel.org/r/5bb55bac6ba10fafab19bf2b21572dd0e2f8cea2.1633593385.git.linux@leemhuis.info
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>doc: fix link to MSG_ZEROCOPY patchset</title>
<updated>2019-03-18T16:50:21+00:00</updated>
<author>
<name>Tobias Klauser</name>
<email>tklauser@distanz.ch</email>
</author>
<published>2019-03-18T11:08:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=25208dd856e74f2b60d053eb98e6dd335816fbc1'/>
<id>urn:sha1:25208dd856e74f2b60d053eb98e6dd335816fbc1</id>
<content type='text'>
Use https and link to the patch directly.

Signed-off-by: Tobias Klauser &lt;tklauser@distanz.ch&gt;
Acked-by: Willem de Bruijn &lt;willemb@google.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>doc: Mention MSG_ZEROCOPY implementation for UDP</title>
<updated>2019-02-17T23:30:02+00:00</updated>
<author>
<name>Petr Vorel</name>
<email>pvorel@suse.cz</email>
</author>
<published>2019-02-14T23:43:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=31a1b8d528fa4aedaa207b38d7fafc4e9b0a0d6c'/>
<id>urn:sha1:31a1b8d528fa4aedaa207b38d7fafc4e9b0a0d6c</id>
<content type='text'>
MSG_ZEROCOPY implementation for UDP was merged in v5.0,
6e360f733113 ("Merge branch 'udp-msg_zerocopy'").

Signed-off-by: Petr Vorel &lt;pvorel@suse.cz&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sock: remove zerocopy sockopt restriction on closed tcp state</title>
<updated>2018-03-14T16:51:28+00:00</updated>
<author>
<name>Willem de Bruijn</name>
<email>willemb@google.com</email>
</author>
<published>2018-03-14T16:49:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=ced68234b6a244355aeab07c2681bc49f695eaed'/>
<id>urn:sha1:ced68234b6a244355aeab07c2681bc49f695eaed</id>
<content type='text'>
Socket option SO_ZEROCOPY determines whether the kernel ignores or
processes flag MSG_ZEROCOPY on subsequent send calls. This to avoid
changing behavior for legacy processes.

Limiting the state change to closed sockets is annoying with passive
sockets and not necessary for correctness. Once created, zerocopy skbs
are processed based on their private state, not this socket flag.

Remove the constraint.

Signed-off-by: Willem de Bruijn &lt;willemb@google.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>doc: clarification about setting SO_ZEROCOPY</title>
<updated>2018-01-10T20:01:49+00:00</updated>
<author>
<name>Kornilios Kourtis</name>
<email>kou@zurich.ibm.com</email>
</author>
<published>2018-01-09T08:52:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=af60d61fa846725566f4a876ae04f891bdff1c7a'/>
<id>urn:sha1:af60d61fa846725566f4a876ae04f891bdff1c7a</id>
<content type='text'>
Signed-off-by: Kornilios Kourtis &lt;kou@zurich.ibm.com&gt;
Acked-by: Willem de Bruijn &lt;willemb@google.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>doc: document MSG_ZEROCOPY</title>
<updated>2017-09-01T17:39:35+00:00</updated>
<author>
<name>Willem de Bruijn</name>
<email>willemb@google.com</email>
</author>
<published>2017-09-01T16:01:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=cc8889ae8298ebfc6bbf52ad98fe3b5afdf4ae70'/>
<id>urn:sha1:cc8889ae8298ebfc6bbf52ad98fe3b5afdf4ae70</id>
<content type='text'>
Documentation for this feature was missing from the patchset.
Copied a lot from the netdev 2.1 paper, addressing some small
interface changes since then.

Changes
  v1 -&gt; v2
    - change email discussion URL format
    - clarify that u32 counter is per-syscall, unsigned and
      wraps after UINT_MAX calls
    - describe errno on send failure specific to MSG_ZEROCOPY
    - a few very minor rewordings

Signed-off-by: Willem de Bruijn &lt;willemb@google.com&gt;
Acked-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
