linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Fix up workarounds for dietlibc breakage
Date: Thu, 9 Jan 2014 10:25:55 -0500	[thread overview]
Message-ID: <20140109152555.GA6192@thunk.org> (raw)
In-Reply-To: <18FF1403-0799-4877-88F2-31FC6D960F03@dilger.ca>

On Wed, Jan 08, 2014 at 08:59:54PM -0700, Andreas Dilger wrote:
> Before e2fsprogs used posix_memalign() the MMP code just allocated a
> 2x sized buffer, and then picked the region in the middle that was
> page aligned.  I'd be fine going back to this to reduce the dependency
> on this interface.

Yeah, I've considered doing that.  It's only a single block, so we'd
only be wasting 4k of memory.

OTOH, there are patches floating around that add posix_memalign()
support to dietlibc.  IIRC, they are included in Fedora at the very
least.  What I don't know is why they aren't in the upstream
distribution.  Did someone not bother to send them upstream, or did
Felix nix them for some reason?  I have on my low priority todo list
to try to follow up on this, and that's why I haven't tried doing the
2x sized buffer thing.

BTW, if we are going to do the 2x buffer thing, we should be doing
that in unix_io.c, which already has direct I/O support.  There's a
lot of duplicate code ext2fs_mmp_read() and ext2fs_mmp_write(); my bad
for noticing this when I accepted the MMP patches.

	 					- Ted

P.S.  BTS, there is an e-mail trail of Felix refusing to fix the
"dietlibc ignores the TZ environment variable" complaint.  I think he
thought the timezone code that they were using was too hairy already,
and the primary use case of dietlibc was one where it was unlikely
that the TZ variable would be used.

      reply	other threads:[~2014-01-09 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  3:26 [PATCH] Fix up workarounds for dietlibc breakage Theodore Ts'o
2014-01-09  3:59 ` Andreas Dilger
2014-01-09 15:25   ` Theodore Ts'o [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=20140109152555.GA6192@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    /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).