From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: using the scalable vmapi API again
Date: Mon, 15 Feb 2010 09:48:07 -0500 [thread overview]
Message-ID: <20100215144807.GA9932@infradead.org> (raw)
Hi Alex,
I've worked with Nick to make sure the regressions introduced by Nick's
scalable vmap API are fixed, so we an start using it again after we
had to disable it after a brief period in early 2009.
Can you make sure commits d2859751cd0bf586941ffa7308635a293f943c17 and
95f8e302c04c0b0c6de35ab399a5551605eeb006 get re-aplied to the XFS
tree, or maybe re-revert their revert commits
3a011a171906a3a51a43bb860fb7c66a64cab140 and
cf7dab801796b9ee52a6dc99888a66bf476538ec.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-02-15 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 14:48 Christoph Hellwig [this message]
2010-03-04 10:43 ` using the scalable vmapi API again 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=20100215144807.GA9932@infradead.org \
--to=hch@infradead.org \
--cc=aelder@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