linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Henderson <allison.henderson@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Cc: Shirley Ma <shirley.ma@oracle.com>
Subject: Re: Status report 3/18 - 3/22
Date: Fri, 22 Mar 2019 18:29:07 -0700	[thread overview]
Message-ID: <2b46c574-6a30-ec97-6369-02ffe3334cea@oracle.com> (raw)
In-Reply-To: <270152f8-f3e2-3e4b-aec5-a623a06aa773@oracle.com>

Oops, wrong mailing list!  Please ignore!

On 3/22/19 5:10 PM, Allison Henderson wrote:
> Status report 3/18 - 3/22
> 
> [1] PMEM bug and performance
> https://bug.oraclecorp.com/pls/bug/webbug_print.show?c_rptno=29494898
>    Attended XFS performance meeting to discuss performance differences 
> seen between xfs and ext4
>    Need to understand why performance increase is only seen when double 
> write featured is enabled
>    Need to wait for block trace output for further analysis
> 
>    Fix for xfs crash on pmem moved to bugzilla to release fix
>    http://ca-bugzilla.us.oracle.com/bugzilla/show_bug.cgi?id=47146
> 
> [2] XFS Parent Pointer update
>    Started updating previous parent pointer solution onto latest 
> development code
>    Some adjustments needed for delayed operations and protofiles
>    Will send out set for review once all the bugs are worked out again
> 
> [3] Patches reviewed:
>     [PATCH] xfs: serialize unaligned dio writes against all other dio 
> writes
> 
> Thanks everyone!
> Allison

      reply	other threads:[~2019-03-23  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23  0:10 Status report 3/18 - 3/22 Allison Henderson
2019-03-23  1:29 ` Allison Henderson [this message]

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=2b46c574-6a30-ec97-6369-02ffe3334cea@oracle.com \
    --to=allison.henderson@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=shirley.ma@oracle.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;
as well as URLs for NNTP newsgroup(s).