From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfs: remove xfs_trans_get_block_res
Date: Wed, 17 Feb 2016 00:57:09 -0800 [thread overview]
Message-ID: <20160217085709.GA9492@infradead.org> (raw)
In-Reply-To: <1455699159-20906-1-git-send-email-hch@lst.de>
Sorry - seems like I sent without the cover letter.
Rational: the xfs_trans_alloc + xfs_trans_reserve combination is
super confusing, and when recently debugging the block reservation
issues in the reflink code I got reminded of my old series to sort
this out, so I dusted it off, tested it and here were are.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-02-17 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:52 [PATCH 1/3] xfs: remove xfs_trans_get_block_res Christoph Hellwig
2016-02-17 8:52 ` [PATCH 2/3] xfs: better xfs_trans_alloc interface Christoph Hellwig
2016-02-17 13:40 ` Brian Foster
2016-02-17 22:04 ` Dave Chinner
2016-02-18 12:10 ` Brian Foster
2016-02-22 13:39 ` Christoph Hellwig
2016-02-22 21:14 ` Dave Chinner
2016-02-17 8:52 ` [PATCH 3/3] xfs: remove transaction types Christoph Hellwig
2016-02-17 8:57 ` Christoph Hellwig [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=20160217085709.GA9492@infradead.org \
--to=hch@infradead.org \
--cc=hch@lst.de \
--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