| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs-trace-ilock-more |
| From: | Mark Fasheh <mfasheh@xxxxxxx> |
| Date: | Wed, 14 Dec 2011 10:27:50 -0800 |
| Cc: | xfs@xxxxxxxxxxx, Jeff Mahoney <jeffm@xxxxxxxx> |
| In-reply-to: | <20111214024040.GA17780@xxxxxxxxxxxxx> |
| Organization: | SUSE Labs |
| References: | <20111214024040.GA17780@xxxxxxxxxxxxx> |
| Reply-to: | Mark Fasheh <mfasheh@xxxxxxx> |
| User-agent: | Mutt/1.5.9i |
Hey Christoph, On Tue, Dec 13, 2011 at 09:40:40PM -0500, Christoph Hellwig wrote: > Can you explain the story behid this patch in SLES11SP1? We were looking at some performance issues and needed a bit more information on the amount of time spent in ilock. I can give you more specifics if you want, I just have to dig up the e-mails (it's been a while). Regards, Mark -- Mark Fasheh |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 10/11] xfs: always return with the iolock held from xfs_file_aio_write_checks, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [RFC, PATCH 0/12] xfs: compound buffers for directory blocks, Christoph Hellwig |
| Previous by Thread: | xfs-trace-ilock-more, Christoph Hellwig |
| Next by Thread: | Re: xfs-trace-ilock-more, Jeff Mahoney |
| Indexes: | [Date] [Thread] [Top] [All Lists] |