From: Alex Bligh <alex@alex.org.uk>
To: netdev <netdev@vger.kernel.org>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Alex Bligh <alex@alex.org.uk>,
"Trond Myklebust" <Trond.Myklebust@netapp.com>,
Mel Gorman <mgorman@suse.de>
Subject: [RFC] rebase Ian Campbell's skb fragment tracking to 3.2
Date: Fri, 25 Jan 2013 14:27:00 +0000 [thread overview]
Message-ID: <1359124027-1170-1-git-send-email-alex@alex.org.uk> (raw)
This patch set, generated by Mel Gorman, rebases Ian Campbell's
fragment tracking code to 3.2. Obviously this does not rebase
it to the current development head, but I thought this might
series might be useful to someone.
The reason for this patch set can be found in the following
links:
http://www.spinics.net/lists/linux-nfs/msg34783.html
http://lists.xen.org/archives/html/xen-devel/2012-12/msg01154.html
The original problem ishere (from 2008!):
http://marc.info/?l=linux-nfs&m=122424132729720&w=2
I've not copiedevery maintainer as this is really only for
information given it's not rebased to head.
next reply other threads:[~2013-01-25 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 14:27 Alex Bligh [this message]
2013-01-25 14:27 ` [RFC] [PATCH 1/7] net: add support for per-paged-fragment destructors Alex Bligh
2013-01-25 14:27 ` [RFC] [PATCH 2/7] net: only allow paged fragments with the same destructor to be coalesced Alex Bligh
2013-01-25 14:27 ` [RFC] [PATCH 3/7] net: add paged frag destructor support to kernel_sendpage Alex Bligh
2013-01-25 14:27 ` [RFC] [PATCH 4/7] sunrpc: use SKB fragment destructors to delay completion until page is released by network stack Alex Bligh
2013-01-25 14:27 ` [RFC] [PATCH 5/7] net: move skb frag kmap functions to skbuff.h Alex Bligh
2013-01-25 14:27 ` [RFC] [PATCH 6/7] net: add skb_frag_k(un)map convenience functions Alex Bligh
2013-01-25 14:27 ` [RFC] [PATCH 7/7] net: return a *const* struct page from skb_frag_page Alex Bligh
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=1359124027-1170-1-git-send-email-alex@alex.org.uk \
--to=alex@alex.org.uk \
--cc=Ian.Campbell@citrix.com \
--cc=Trond.Myklebust@netapp.com \
--cc=mgorman@suse.de \
--cc=netdev@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.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).