All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] extend e2fsprogs functionality to add EXT2_FLAG_DIRECT option
Date: Mon, 11 Jan 2010 15:06:58 -0500	[thread overview]
Message-ID: <4B4B84E2.1050508@redhat.com> (raw)
In-Reply-To: <4B46FCB2.1090308@redhat.com>

On 01/08/2010 04:36 AM, Michal Novotny wrote:
> This patch extends functionality of e{2|4}fsprogs to add 
> EXT2_FLAG_DIRECT flag to be passed to ext2fs_open2() function. This 
> internally calls open() function with O_DIRECT and handles the memory 
> alignment for both read and write operations.
> In some cases direct access to devices is necessary and that was the 
> main reason for this patch to be done.
>
> The main reason why this was done is that pygrub (used by xen 
> virtualization user-space package, it's a python version of grub for 
> paravirtualized guests) sometimes uses outdated version of grub.conf 
> file. Modifications to xen package were *not* enough because e2fsprogs 
> doesn't open the files directly. That's why I added EXT2_FLAG_DIRECT 
> support to make read/write operations work directly when passed. It's 
> been tested with pygrub like mentioned above for read operation and 
> it's working fine.
>
> Signed-off-by: Michal Novotny <minovotn@redhat.com>

Can you add to this some kind of data flow overview?  Seems like a 
really odd way to update this file system...

ric


  reply	other threads:[~2010-01-11 20:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  9:36 [PATCH] extend e2fsprogs functionality to add EXT2_FLAG_DIRECT option Michal Novotny
2010-01-11 20:06 ` Ric Wheeler [this message]
2010-01-12 10:54   ` Michal Novotny
2010-01-12 11:59     ` Ric Wheeler
2010-01-12 12:15       ` Michal Novotny
2010-01-12 12:23         ` Christoph Hellwig
2010-01-12 12:30           ` Michal Novotny
2010-01-12 12:46             ` Christoph Hellwig
2010-01-12 13:01               ` Michal Novotny
2010-01-12 13:04                 ` Ric Wheeler
2010-01-12 13:12                   ` Michal Novotny
2010-01-12 13:23                     ` Michal Novotny
2010-01-12 13:29                       ` Ric Wheeler
2010-01-12 13:33                         ` Michal Novotny
2010-01-12 14:33                           ` Chris Lee
2010-01-12 14:37                             ` Michal Novotny
2010-01-12 16:38                 ` Christoph Hellwig
2010-01-12 16:43                   ` Michal Novotny
2010-01-12 16:47                     ` Christoph Hellwig
2010-01-12 16:51                       ` Michal Novotny
2010-01-12 16:50                     ` Ric Wheeler
2010-01-12 16:53                       ` Michal Novotny
2010-01-12 16:56                         ` Eric Sandeen
2010-01-12 16:59                           ` Ric Wheeler
2010-01-12 17:00                             ` Michal Novotny
2010-01-14 13:46                               ` Michal Novotny
2010-01-12 12:47             ` Andreas Dilger
2010-01-12 13:04               ` Michal Novotny
2010-01-12 15:16           ` Eric Sandeen
2010-01-12 15:46             ` Michal Novotny
2010-01-12 20:01               ` Ric Wheeler

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=4B4B84E2.1050508@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=minovotn@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.