From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] [RFC] xfs: stop using the page cache to back the buffer cache
Date: Wed, 12 Jan 2011 08:16:05 -0500 [thread overview]
Message-ID: <20110112131604.GA28675@infradead.org> (raw)
In-Reply-To: <1294817201-18670-1-git-send-email-david@fromorbit.com>
> - if (bp->b_pages != bp->b_page_array) {
> + if (bp->b_pages && bp->b_pages != bp->b_page_array) {
If bp->p_ages is NULL it's per defintion different from b_page_array.
> STATIC int
> -_xfs_buf_lookup_pages(
> +xfs_buf_allocate_buffer(
This is a bit misnamed and rather confusing vs xfs_buf_allocate.
Maybe call it xfs_buf_allocate_memory?
> + /*
> + * for buffers that are contained within a single page, just allocate
> + * the memory from the heap - there's no need for the complexity of
> + * page arrays to keep allocation down to order 0.
> + */
> + if (bp->b_buffer_length <= PAGE_SIZE) {
I think this should be a <, not <= - for page sized buffers avoiding
the slab overhead should be much more efficient.
> + page_count = 1;
> + } else {
> + end = bp->b_file_offset + bp->b_buffer_length;
> + page_count = xfs_buf_btoc(end) -
> + xfs_buf_btoct(bp->b_file_offset);
> + }
>
> error = _xfs_buf_get_pages(bp, page_count, flags);
> if (unlikely(error))
> return error;
> +
> + if (bp->b_page_count == 1) {
I'd just duplicate the _xfs_buf_get_pages inside the branches to make
this a lot cleaner. The page_count calculation in the else clause can
never end up as 1 anyway. Maybe even make it two different functions
and let the only caller decide which one to use.
> + unsigned long pageaddr;
> +
> + bp->b_addr = kmem_alloc(bp->b_buffer_length, xb_to_km(flags));
> + if (!bp->b_addr)
> + return ENOMEM;
> +
> + pageaddr = (unsigned long)bp->b_addr & PAGE_MASK;
> + ASSERT(((unsigned long)(bp->b_addr + bp->b_buffer_length - 1) & PAGE_MASK) == pageaddr);
> +
> + bp->b_offset = (unsigned long)bp->b_addr - pageaddr;
This can just be
bp->b_offset = offset_in_page(bp->b_addr);
> + bp->b_pages[0] = virt_to_page((void *)pageaddr);
and this
bp->b_pages[0] = virt_to_page(bp->b_addr);
with that the above assert can be changed to not need a local variable
and imho be slightly cleaner:
ASSERT(((unsigned long)bp->b_addr + bp->b_buffer_length - 1) &
PAGE_MASK) ==
(unsigned long)bp->b_addr & PAGE_MASK);
although I'm not sure it's actually correct. slub is a pretty
aggressive in using high order pages and might give us back memory that
goes across multiple pages. Adding a loop here to assign multiple pages
if needed seems safer.
> + bp->b_flags |= XBF_MAPPED|_XBF_KMEM;
Space around the | operator, please.
> + bp->b_flags &= XBF_MAPPED|_XBF_KMEM|_XBF_PAGES;
here, too.
Additional comments:
- the _XBF_PAGE_CACHE and _XBF_PAGE_LOCKED flags are now unused and can
be removed.
- the comment describing xfs_buf_t around line 141 in xfs_buf.h is now
incorrect. It's not overly useful so I'd suggest removing it
completely.
- the comments above the buffer locking functions in xfs_buf.c
(including the meta-comment) are now incorrect and should be
fixed/removed.
- the call to mark_page_accessed in xfs_buf_get is now superflous,
as it only has a meaning for pagecache pages.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-12 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 7:26 [PATCH] [RFC] xfs: stop using the page cache to back the buffer cache Dave Chinner
2011-01-12 13:16 ` Christoph Hellwig [this message]
2011-01-12 13:22 ` Christoph Hellwig
2011-01-12 21:15 ` 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=20110112131604.GA28675@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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.