public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Brian Foster <bfoster@redhat.com>,
	linux-xfs@vger.kernel.org, tom.leiming@gmail.com,
	vkuznets@redhat.com
Subject: Re: [PATCH v2] xfs: use a dedicated SLAB cache for sector sized buffer data
Date: Thu, 6 Dec 2018 10:00:33 -0800	[thread overview]
Message-ID: <20181206180033.GO24487@magnolia> (raw)
In-Reply-To: <20181206151715.GA25967@lst.de>

On Thu, Dec 06, 2018 at 04:17:15PM +0100, Christoph Hellwig wrote:
> On Thu, Dec 06, 2018 at 07:51:52AM -0500, Brian Foster wrote:
> > On Wed, Dec 05, 2018 at 02:51:47PM -0800, Christoph Hellwig wrote:
> > > XFS currently uses kmalloc for buffers smaller than the page size to
> > > avoid wasting too much memory.  But this can cause a problem with slub
> > > debugging turned on as the allocations might not be naturally aligned.
> > > On block devices that require sector size alignment this can lead to
> > > data corruption.
> > > 
> > > Give that our smaller than page size buffers are always sector sized
> > > on a live file system, we can just create a kmem_cache with an
> > > explicitly specified alignment requirement for this case to fix this
> > > case without much effort.
> > > 
> > 
> > What exactly is the data corruption related problem? Can you
> > characterize it in a couple sentences?
> 
> Ming reported the actual occurance, so he can explain in detail.  But
> the summary is that various devices require a minimum alignment for DMA,
> and if we don't follow that bad things will happen.  What "bad things"
> are might vary from case to case.

I think it's worth mentioning in the comment that we're doing aligned
slab cache thing to avoid screwing up certain devices' DMA requirements
for IO requests, even if we leave out the particulars of what 'bad
things' means.

--D

  reply	other threads:[~2018-12-06 18:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 22:51 [PATCH v2] xfs: use a dedicated SLAB cache for sector sized buffer data Christoph Hellwig
2018-12-06  0:59 ` Dave Chinner
2018-12-06 12:51 ` Brian Foster
2018-12-06 15:17   ` Christoph Hellwig
2018-12-06 18:00     ` Darrick J. Wong [this message]
2018-12-06 21:38   ` Dave Chinner
2018-12-06 17:22 ` Nikolay Borisov
2018-12-06 18:11 ` Darrick J. Wong
2018-12-06 20:11   ` Christoph Hellwig
2018-12-06 20:26     ` Darrick J. Wong
2018-12-06 20:39       ` Brian Foster
2018-12-06 21:33     ` Dave Chinner
2018-12-07 10:14     ` Ming Lei
2018-12-07 15:21 ` Vitaly Kuznetsov

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=20181206180033.GO24487@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tom.leiming@gmail.com \
    --cc=vkuznets@redhat.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