From: Christoph Hellwig <hch@lst.de>
To: Shailendra Tripathi <stripathi@agami.com>
Cc: Christoph Hellwig <hch@lst.de>,
xfs@oss.sgi.com, ecashin@coraid.com, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: stop using kmalloc in xfs_buf_get_noaddr
Date: Wed, 7 Mar 2007 13:38:24 +0100 [thread overview]
Message-ID: <20070307123824.GA3996@lst.de> (raw)
In-Reply-To: <45EEACA0.4050206@agami.com>
On Wed, Mar 07, 2007 at 05:44:24PM +0530, Shailendra Tripathi wrote:
> Hi Christoph,
> Did you do some testing for recovery when end of the physical
> log is seen ?
I ran xfsqa over it, which should catch this case.
> When you will be dealing with striped ICLOG buffers or big
> sized ICLOGs, header size might range from 512 to 2k. Also, this header
> might be split into 2 parts at the end of physical log. Then, you don't
> have page size buffer. Please verify that XFS_BUF_SETP_PTRs work correctly
> for those cases.
> Same thing is true when data section is split around physical log.
> You can get one part which is not PAGE sized.
I should have made my wording more clear, we always do PAGE_SIZE +
buffer allocations. After XFS_BUF_SETP_PTR the actually used buffer
might be smaller. I tested XFS_BUF_SETP_PTR manually with
artifical test code aswell, and made sure it still works.
Long term I have a plan to replace XFS_BUF_SETP_PTR with better
schemes, but that's irrelevant for this patch.
next prev parent reply other threads:[~2007-03-07 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 10:13 [PATCH 2/2] xfs: stop using kmalloc in xfs_buf_get_noaddr Christoph Hellwig
2007-03-07 12:14 ` Shailendra Tripathi
2007-03-07 12:38 ` Christoph Hellwig [this message]
2007-03-07 17:04 ` Michael Nishimoto
2007-03-07 17:15 ` Christoph Hellwig
2007-03-09 11:55 ` Christoph Hellwig
2007-03-13 0:08 ` Timothy Shimmin
2007-03-17 0:36 ` 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=20070307123824.GA3996@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=ecashin@coraid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stripathi@agami.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 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.