public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: nathans@sgi.com (Nathan Scott)
To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com
Subject: PARTIAL TAKE 944409 - DMAPI bulkstat optimisations
Date: Tue, 25 Jul 2006 13:36:09 +1000 (EST)	[thread overview]
Message-ID: <20060725033609.3AC4F58C38C1@chook.melbourne.sgi.com> (raw)

Ensure we specify the type of bulkstat call we will issue
(uninited variable).

Date:  Tue Jul 25 13:31:08 AEST 2006
Workarea:  chook.melbourne.sgi.com:/build/nathans/xfs-linux
Inspected by:  vapo

The following file(s) were checked into:
  longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb


Modid:  xfs-linux-melb:xfs-kern:26601a
dmapi/xfs_dm.c - 1.16 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/dmapi/xfs_dm.c.diff?r1=text&tr1=1.16&r2=text&tr2=1.15&f=h


Rework DMAPI bulkstat calls in such a way that we can directly extract
inline attributes out of the bulkstat buffer (for that case), rather
than using an (extremely expensive for large icount filesystems) iget
for fetching attrs.

Date:  Tue Jul 25 13:34:45 AEST 2006
Workarea:  chook.melbourne.sgi.com:/build/nathans/xfs-linux
Inspected by:  vapo

The following file(s) were checked into:
  longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb


Modid:  xfs-linux-melb:xfs-kern:26602a
xfs_itable.c - 1.141 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_itable.c.diff?r1=text&tr1=1.141&r2=text&tr2=1.140&f=h
xfs_itable.h - 1.49 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_itable.h.diff?r1=text&tr1=1.49&r2=text&tr2=1.48&f=h
dmapi/xfs_dm.c - 1.17 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/dmapi/xfs_dm.c.diff?r1=text&tr1=1.17&r2=text&tr2=1.16&f=h

                 reply	other threads:[~2006-07-25  3:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060725033609.3AC4F58C38C1@chook.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sgi.bugs.xfs@engr.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