From: Matthew Hodgson <matthew@mxtelecom.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Zero-copy Block IO with XFS
Date: Wed, 12 Dec 2007 11:20:44 +0000 [thread overview]
Message-ID: <475FC40C.3030102@mxtelecom.com> (raw)
In-Reply-To: <20071212110735.GH4612@sgi.com>
Hi Dave,
Thanks for the response :)
David Chinner wrote:
> On Tue, Dec 11, 2007 at 11:38:19AM +0000, Matthew Hodgson wrote:
>> I'm experimenting with using XFS with a network block device (DST), and
>> have come up against the problem that when writing data to the network,
>> it uses kernel_sendpage to hand the page presented at the BIO layer to
>> the network stack. It then completes the block IO request.
>>
>> The problem arises when XFS proceeds to then reuse that page before the
>> NIC actually sends it.
>
> Where does XFS overwrite a page while I/O is still in progress?
> Stack trace please.
It doesn't. The problem is that after the block device has completed
the IO request with bio_endio(), there's a risk that it may still need
access to the page in order to retransmit it, perform offloaded
checksumming, etc.
>> Particularly if TX checksumming or TCP
>> segmentation is being offloaded to the NIC, it seems that the NIC will
>> try to access to page after the BIO request has returned, and so operate
>> on stale data.
>
> That sounds like you are completing the bio before the I/O has
> really been completed. Basically, the bio can't be completed until
> the data has been sent and that will prevent any use after free or
> overwrite of the data while it is being sent...
Agreed. In general that will cause a fairly major performance hit,
however (you'd have to at least wait for the ACK from the TCP peer
before completing the BIO). Or make a copy of the page. Is there no
scope (however theoretical - I guess this is starting to become an
academic question) for providing XFS with hints that particular pages
are in use elsewhere and should not be overwritten? Could XFS mandate
only overwriting pages in its cache with a ->count of 1?
In other news, does XFS still provide the block layer with
slab-allocated pages for metadata operations?
thanks,
Matthew.
--
Matthew Hodgson <matthew@mxtelecom.com>
Media & Systems Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
prev parent reply other threads:[~2007-12-12 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 11:38 Zero-copy Block IO with XFS Matthew Hodgson
2007-12-11 16:39 ` Bhagi rathi
2007-12-12 1:52 ` Matthew Hodgson
2007-12-12 11:07 ` David Chinner
2007-12-12 11:20 ` Matthew Hodgson [this message]
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=475FC40C.3030102@mxtelecom.com \
--to=matthew@mxtelecom.com \
--cc=dgc@sgi.com \
--cc=xfs@oss.sgi.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