All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Allocate reservation during write_begin if needed
Date: Tue, 17 Feb 2015 19:19:56 +0000	[thread overview]
Message-ID: <54E3945C.6050606@redhat.com> (raw)
In-Reply-To: <2063966524.14688631.1424200190610.JavaMail.zimbra@redhat.com>

Hi,

On 17/02/15 19:09, Bob Peterson wrote:
> ----- Original Message -----
>> Hi,
>>
>>
>> Since we set the allocation structure when the write call begins, and it
>> is not deallocated until there are no writers left with the file open,
>> how does this happen?
>>
>> Steve.
> Hi,
>
> In a normal write, the code goes through gfs2_page_mkwrite or
> gfs2_file_aio_write. In the failing scenario, it's going through
> sendfile. I suppose I could patch sendfile as an alternative, but
> the advantage here is that this patch will do it only if a block
> allocation is needed.
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems

Ah, I see. In which case that code path should be patched. So it should 
be part of the splice code I think, since it should be done at the 
higher level, and not at the write_begin level, since that is too late. 
We should have a call to the reservation code too at that point, to 
ensure that we don't have fragmentation issues. So we need a wrapper for 
|iter_file_splice_write| along the lines of gfs2_file_write_iter I think,

Steve.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20150217/5af83d4a/attachment.htm>

      reply	other threads:[~2015-02-17 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <651143083.14528614.1424192729406.JavaMail.zimbra@redhat.com>
2015-02-17 17:09 ` [Cluster-devel] [GFS2 PATCH] GFS2: Allocate reservation during write_begin if needed Bob Peterson
2015-02-17 19:00   ` Steven Whitehouse
2015-02-17 19:09     ` Bob Peterson
2015-02-17 19:19       ` Steven Whitehouse [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=54E3945C.6050606@redhat.com \
    --to=swhiteho@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.