From: Shailendra Tripathi <stripathi@agami.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com, ecashin@coraid.com, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs: use xfs_get_buf_noaddr for iclogs
Date: Wed, 07 Mar 2007 17:29:40 +0530 [thread overview]
Message-ID: <45EEA92C.9080505@agami.com> (raw)
In-Reply-To: <20070307101314.GB30587@lst.de>
Does not look to me either. Looks logical as well because these buffers
are used only in log syncing and only one thread can be ever flushing
one ICLOG and, hence, no need for protection.
Even split buffer (log->l_xbuf) is used by only ICLOG at a time,
should not matter. I don't see protection for this even today as no
locking is done in split sync path.
-shailendra
Christoph Hellwig wrote:
> Currently xlog_alloc allocates memory for the iclogs first, then
> allocates a buffer using xfs_buf_get_empty and finally assigns
> the memory to the buffer. We don't really want to do this, but
> rather allocate a buffer with memory attached to it using
> xfs_buf_get_noaddr. There's a subtile change because
> xfs_buf_get_empty returns the buffer locked, but xfs_buf_get_noaddr
> returns it unlocked. From my auditing and testing nothing in the
> log I/O code cares about this distincition, but I'd be happy if
> someone could try to prove this independently.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Index: linux-2.6/fs/xfs/xfs_log.c
> ===================================================================
> --- linux-2.6.orig/fs/xfs/xfs_log.c 2007-03-06 17:26:40.000000000 +0100
> +++ linux-2.6/fs/xfs/xfs_log.c 2007-03-06 17:28:03.000000000 +0100
> @@ -1199,11 +1199,16 @@
> *iclogp = (xlog_in_core_t *)
> kmem_zalloc(sizeof(xlog_in_core_t), KM_SLEEP);
> iclog = *iclogp;
> - iclog->hic_data = (xlog_in_core_2_t *)
> - kmem_zalloc(iclogsize, KM_SLEEP | KM_LARGE);
> -
> iclog->ic_prev = prev_iclog;
> prev_iclog = iclog;
> +
> + bp = xfs_buf_get_noaddr(log->l_iclog_size, mp->m_logdev_targp);
> + XFS_BUF_SET_IODONE_FUNC(bp, xlog_iodone);
> + XFS_BUF_SET_BDSTRAT_FUNC(bp, xlog_bdstrat_cb);
> + XFS_BUF_SET_FSPRIVATE2(bp, (unsigned long)1);
> + iclog->ic_bp = bp;
> + iclog->hic_data = bp->b_addr;
> +
> log->l_iclog_bak[i] = (xfs_caddr_t)&(iclog->ic_header);
>
> head = &iclog->ic_header;
> @@ -1216,11 +1221,6 @@
> INT_SET(head->h_fmt, ARCH_CONVERT, XLOG_FMT);
> memcpy(&head->h_fs_uuid, &mp->m_sb.sb_uuid, sizeof(uuid_t));
>
> - bp = xfs_buf_get_empty(log->l_iclog_size, mp->m_logdev_targp);
> - XFS_BUF_SET_IODONE_FUNC(bp, xlog_iodone);
> - XFS_BUF_SET_BDSTRAT_FUNC(bp, xlog_bdstrat_cb);
> - XFS_BUF_SET_FSPRIVATE2(bp, (unsigned long)1);
> - iclog->ic_bp = bp;
>
> iclog->ic_size = XFS_BUF_SIZE(bp) - log->l_iclog_hsize;
> iclog->ic_state = XLOG_STATE_ACTIVE;
> @@ -1229,7 +1229,6 @@
> iclog->ic_datap = (char *)iclog->hic_data + log->l_iclog_hsize;
>
> ASSERT(XFS_BUF_ISBUSY(iclog->ic_bp));
> - ASSERT(XFS_BUF_VALUSEMA(iclog->ic_bp) <= 0);
> sv_init(&iclog->ic_forcesema, SV_DEFAULT, "iclog-force");
> sv_init(&iclog->ic_writesema, SV_DEFAULT, "iclog-write");
>
> @@ -1528,7 +1527,6 @@
> }
> #endif
> next_iclog = iclog->ic_next;
> - kmem_free(iclog->hic_data, log->l_iclog_size);
> kmem_free(iclog, sizeof(xlog_in_core_t));
> iclog = next_iclog;
> }
>
>
next prev parent reply other threads:[~2007-03-07 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 10:13 [PATCH 1/2] xfs: use xfs_get_buf_noaddr for iclogs Christoph Hellwig
2007-03-07 11:59 ` Shailendra Tripathi [this message]
2007-03-12 4:41 ` David Chinner
2007-03-17 0:35 ` 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=45EEA92C.9080505@agami.com \
--to=stripathi@agami.com \
--cc=akpm@osdl.org \
--cc=ecashin@coraid.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.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