From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: brouer@redhat.com, netdev@vger.kernel.org, davem@davemloft.net,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next] doc: document MSG_ZEROCOPY
Date: Fri, 1 Sep 2017 14:44:24 +0200 [thread overview]
Message-ID: <20170901144424.72f9c9e9@redhat.com> (raw)
In-Reply-To: <20170831210013.85220-1-willemdebruijn.kernel@gmail.com>
On Thu, 31 Aug 2017 17:00:13 -0400
Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote:
> +More Info
> +---------
> +
> +Much of this document was derived from a longer paper presented at
> +netdev 2.1. For more in-depth information see that paper and talk,
> +the excellent reporting over at LWN.net or read the original code.
> +
> + paper, slides, video
> + https://netdevconf.org/2.1/session.html?debruijn
> +
> + LWN article
> + https://lwn.net/Articles/726917/
> +
> + patchset
> + [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY
> + https://lwn.net/Articles/730010/
> + https://www.spinics.net/lists/netdev/msg447552.html
IMHO I think it would be better to use the type links also used in the
git log. If you look at the kernel git log, then the "Link:" tag have
the form: http://lkml.kernel.org/r/
And you can simply append the "Message-Id:" email header.
In this case the link would be:
http://lkml.kernel.org/r/20170803202945.70750-1-willemdebruijn.kernel@gmail.com
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2017-09-01 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 21:00 [PATCH net-next] doc: document MSG_ZEROCOPY Willem de Bruijn
2017-09-01 2:10 ` Alexei Starovoitov
2017-09-01 3:04 ` Willem de Bruijn
2017-09-01 3:10 ` Alexei Starovoitov
2017-09-01 3:31 ` Willem de Bruijn
2017-09-01 15:47 ` Willem de Bruijn
2017-09-01 12:44 ` Jesper Dangaard Brouer [this message]
2017-09-01 13:37 ` Willem de Bruijn
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=20170901144424.72f9c9e9@redhat.com \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@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 NNTP newsgroup(s).