From: Christoph Hellwig <hch@lst.de>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Christoph Hellwig <hch@lst.de>,
hughd@google.com, hirofumi@mail.parknet.co.jp,
chris.mason@oracle.com, swhiteho@redhat.com,
linux-fsdevel@vger.kernel.org, jaxboe@fusionio.com,
martin.petersen@oracle.com
Subject: Re: discard and barriers
Date: Sun, 15 Aug 2010 23:30:13 +0200 [thread overview]
Message-ID: <20100815213013.GA17594@lst.de> (raw)
In-Reply-To: <20100815212534.GE20124@thunk.org>
On Sun, Aug 15, 2010 at 05:25:34PM -0400, Ted Ts'o wrote:
> OK, now I understand why I'm confused. I thought the proposal was to
> change sb_issue_discard() to make it be asynchronous? Really, what
> we're talking about here is eliminating the explicit
> barrier/SYNCHRONIZE CACHE from the discard, correct? The
> sb_issue_discard() call will still remain synchronous.
Yes, at least for now. I don't think keeping it that way over the long
run is a good idea, but for now getting rid of the barrier is all that
*needs* to be done. The rest is optimizations that can be done later.
next prev parent reply other threads:[~2010-08-15 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 11:56 discard and barriers Christoph Hellwig
2010-08-14 14:14 ` Ted Ts'o
2010-08-14 14:52 ` Christoph Hellwig
2010-08-14 15:46 ` Chris Mason
2010-08-14 17:22 ` Christoph Hellwig
2010-08-14 20:11 ` Hugh Dickins
2010-08-15 17:39 ` Ted Ts'o
2010-08-15 19:02 ` Christoph Hellwig
2010-08-15 21:25 ` Ted Ts'o
2010-08-15 21:30 ` Christoph Hellwig [this message]
2010-08-16 9:41 ` Steven Whitehouse
2010-08-16 11:26 ` Christoph Hellwig
2010-08-17 10:59 ` Steven Whitehouse
2010-08-23 16:42 ` Christoph Hellwig
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=20100815213013.GA17594@lst.de \
--to=hch@lst.de \
--cc=chris.mason@oracle.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=hughd@google.com \
--cc=jaxboe@fusionio.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=swhiteho@redhat.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.