From: David Miller <davem@davemloft.net>
To: Ian.Campbell@citrix.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/6] net: pad skb data and shinfo as a whole rather than individually
Date: Sat, 07 Jan 2012 10:18:20 -0800 (PST) [thread overview]
Message-ID: <20120107.101820.1395301647780373402.davem@davemloft.net> (raw)
In-Reply-To: <1325793658.29084.21.camel@dagon.hellion.org.uk>
From: Ian Campbell <Ian.Campbell@citrix.com>
Date: Thu, 5 Jan 2012 20:00:58 +0000
> Although this scheme works fine for Xen's netback I don't think it works
> for other use cases like the NFS one (or basically any kernel_sendpage
> usage). In those cases you don't want to wait for the last core mm ref
> on the page to get dropped, you just want to wait for the last ref due
> to the particular sendpage. If you use the core page_count() reference
> count then you end up waiting for the process to exit (and drop the core
> reference count) before the destructor fires and you can complete the
> write, which is obviously not what is desired!
>
> There's also issues with things like two threads simultaneously doing
> I/O from the same page. If one lot of I/O is to NFS and the other to
> iSCSI (assuming they both use this facility in the future) then they
> will clash over the use of the struct page field. In fact even if they
> were both to NFS I bet nothing good would happen...
Ok, struct page doesn't seem the best place for this stuff then.
Thanks.
next prev parent reply other threads:[~2012-01-07 18:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 17:09 [PATCH 0/6 v2] skb paged fragment destructors Ian Campbell
2012-01-05 17:13 ` [PATCH 1/6] net: pack skb_shared_info more efficiently Ian Campbell
2012-01-05 18:30 ` Eric Dumazet
2012-01-05 19:09 ` David Miller
2012-01-05 17:13 ` [PATCH 2/6] net: pad skb data and shinfo as a whole rather than individually Ian Campbell
2012-01-05 17:46 ` Eric Dumazet
2012-01-05 19:13 ` David Miller
2012-01-05 20:00 ` Ian Campbell
2012-01-07 18:18 ` David Miller [this message]
2012-01-05 19:19 ` Ian Campbell
2012-01-05 20:22 ` Eric Dumazet
2012-01-06 11:20 ` Ian Campbell
2012-01-06 12:33 ` Eric Dumazet
2012-01-06 13:20 ` Ian Campbell
2012-01-06 13:37 ` Eric Dumazet
2012-01-06 13:49 ` Ian Campbell
2012-01-06 13:29 ` Ian Campbell
2012-01-05 17:13 ` [PATCH 3/6] net: add support for per-paged-fragment destructors Ian Campbell
2012-01-06 1:15 ` Michał Mirosław
2012-01-06 8:50 ` Ian Campbell
2012-01-05 17:13 ` [PATCH 4/6] net: only allow paged fragments with the same destructor to be coalesced Ian Campbell
2012-01-05 17:13 ` [PATCH 5/6] net: add paged frag destructor support to kernel_sendpage Ian Campbell
2012-01-05 19:15 ` David Miller
2012-01-05 20:04 ` Ian Campbell
[not found] ` <1325783399.25206.413.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-01-05 17:13 ` [PATCH 6/6] sunrpc: use SKB fragment destructors to delay completion until page is released by network stack Ian Campbell
2012-01-05 17:27 ` [PATCH 0/6 v2] skb paged fragment destructors David Laight
2012-01-05 17:34 ` David Miller
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=20120107.101820.1395301647780373402.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ian.Campbell@citrix.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).