From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 2/9] xfs: convert internal buffer functions to pass maps
Date: Wed, 20 Jun 2012 10:48:45 -0500 [thread overview]
Message-ID: <20120620154845.GK2676@sgi.com> (raw)
In-Reply-To: <20120620063508.GD30705@dastard>
Hey Dave,
On Wed, Jun 20, 2012 at 04:35:08PM +1000, Dave Chinner wrote:
> On Wed, Jun 20, 2012 at 02:04:00AM -0400, Christoph Hellwig wrote:
> > On Wed, Jun 20, 2012 at 03:56:19PM +1000, Dave Chinner wrote:
> > > > they are rebased not to require the inode allocator patchset. I think that Jan
> > > > is also going to repost his 'Fix overallocation in xfs_buf_allocate_memory()'
> > > > based upon Dave's suggestions. It's best not to depend upon that either. What
> > > > do you say, Dave?
> > >
> > > I reorder my local patch set and repost it after running it through
> > > some testing....
> >
> > Sorry, I totally misunderstood the initial issue - I though Ben had my
> > series applied, and thus yours didn't apply.
> >
> > I still think reordering is better - I'm quite busy and I'd rather get
> > your series reviewed first before redoing and retesting the inode
> > allocator changes.
>
> I stand corrected - it doesn't need a rebase - all it needs is to be
> applied on top of Jan Kara's bug fix. Looking back, that's exactly
> what I said in patch 0 of the series....
>
> So it should be good to go as Jan's fix needs to go to Linus before
> 3.5 is released...
Gulp!
When I brought this up I was certain that I couldn't get Dave's series to apply
without Christoph's. Now it works just fine like so:
~/xfs # cat patches/series
# from christoph
xfs-implement-update_time.patch
# from dave
xfs-fix-allocbt-cursor-leak-in-xfs_alloc_ag_vextent_near.patch
# Mark's patches
xfs-rename-log-structure-and-remove-xlog_t-typedef.patch
tmp.eUYwHqCBlD-2
# seek data seek hole with unwritten extents
xfs-probe-data-buffer-from-page-cache-for-unwritten-extents.patch
# from Alain
prefix-io_xx-flags-with-xfs_io_xx-to-avoid-namespace-colision.patch
# jan's patch is gonna get a new rev
xfs-fix-overallocation-in-xfs_buf_allocate_memory.patch
# dave's patches
xfs-separate-buffer-indexing-from-block-map.patch
xfs-convert-internal-buffer-functions-to-pass-maps.patch
xfs-add-discontiguous-buffer-map-interface.patch
xfs-add-discontiguous-buffer-support-to-transactions.patch
xfs-struct-xfs_buf_log_format-isn-t-variable-sized.patch
xfs-support-discontiguous-buffers-in-the-xfs_buf_log_item.patch
xfs-use-multiple-irec-xfs-buf-support-in-dabuf.patch
xfs-remove-struct-xfs_dabuf-and-infrastructure.patch
xfs-factor-buffer-reading-from-xfs_dir2_leaf_getdents.patch
# christoph's patches
xfs-kill-xfs_ialloc_find_free
xfs-split-xfs_dialloc
xfs-simplify-xfs_dialloc
xfs-dialloc-shortcut-second-call
xfs-cleanup-xfs_ialloc_ag_select
xfs-dialloc-cleanup-ag-loop-2
xfs-dialloc-factor-ag_selection-2
# from Jan Englehardt
types.h-implement-intptr_t-and-uintptr_t.patch
xfs-use-standard-u-intptr_t-types.patch
So it appears there is no need to rebase Dave's series. Apologies! I got it
wrong, not sure how.
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-20 15:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 5:38 [PATCH 0/9] xfs: discontiguous directory buffer support Dave Chinner
2012-06-08 5:38 ` [PATCH 1/9] xfs: separate buffer indexing from block map Dave Chinner
2012-06-18 20:39 ` Ben Myers
2012-06-20 6:44 ` Christoph Hellwig
2012-06-20 7:36 ` Dave Chinner
2012-06-08 5:38 ` [PATCH 2/9] xfs: convert internal buffer functions to pass maps Dave Chinner
2012-06-18 20:43 ` Ben Myers
2012-06-18 21:07 ` Ben Myers
2012-06-19 7:15 ` Christoph Hellwig
2012-06-19 15:59 ` Ben Myers
2012-06-19 17:03 ` Christoph Hellwig
2012-06-19 17:11 ` Ben Myers
2012-06-20 5:56 ` Dave Chinner
2012-06-20 6:04 ` Christoph Hellwig
2012-06-20 6:29 ` Dave Chinner
2012-06-20 6:46 ` Dave Chinner
2012-06-20 15:39 ` Ben Myers
2012-06-20 15:36 ` Ben Myers
2012-06-20 23:04 ` Dave Chinner
2012-06-20 6:35 ` Dave Chinner
2012-06-20 15:48 ` Ben Myers [this message]
2012-06-20 6:29 ` Christoph Hellwig
2012-06-20 6:37 ` Dave Chinner
2012-06-20 15:51 ` Ben Myers
2012-06-20 6:48 ` Christoph Hellwig
2012-06-22 6:48 ` Dave Chinner
2012-06-08 5:38 ` [PATCH 3/9] xfs: add discontiguous buffer map interface Dave Chinner
2012-06-20 6:53 ` Christoph Hellwig
2012-06-08 5:38 ` [PATCH 4/9] xfs: add discontiguous buffer support to transactions Dave Chinner
2012-06-20 6:54 ` Christoph Hellwig
2012-06-08 5:38 ` [PATCH 5/9] xfs: struct xfs_buf_log_format isn't variable sized Dave Chinner
2012-06-20 6:36 ` Christoph Hellwig
2012-06-20 7:01 ` Dave Chinner
2012-06-20 7:05 ` Christoph Hellwig
2012-06-08 5:38 ` [PATCH 6/9] xfs: support discontiguous buffers in the xfs_buf_log_item Dave Chinner
2012-06-20 7:15 ` Christoph Hellwig
2012-06-08 5:38 ` [PATCH 7/9] xfs: use multiple irec xfs buf support in dabuf Dave Chinner
2012-06-20 7:18 ` Christoph Hellwig
2012-06-08 5:38 ` [PATCH 8/9] xfs: remove struct xfs_dabuf and infrastructure Dave Chinner
2012-06-20 7:20 ` Christoph Hellwig
2012-06-08 5:38 ` [PATCH 9/9] xfs: factor buffer reading from xfs_dir2_leaf_getdents Dave Chinner
2012-06-20 7:27 ` Christoph Hellwig
2012-06-20 7:41 ` Dave Chinner
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=20120620154845.GK2676@sgi.com \
--to=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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