public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 1/5] mips: Do not malloc on getdents64 fallback
Date: Wed, 28 Aug 2019 21:23:00 -0000	[thread overview]
Message-ID: <87muft9e7d.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <4298ae27-5ba3-e06c-de8b-a338b3547ad7@linaro.org> (Adhemerval Zanella's message of "Wed, 28 Aug 2019 18:02:22 -0300")

* Adhemerval Zanella:

> On 28/08/2019 11:42, Florian Weimer wrote:
>> * Adhemerval Zanella:
>> 
>>>    struct kernel_dirent
>>> +  {
>>> +    unsigned long d_ino;
>>> +    unsigned long d_off;
>>> +    unsigned short int d_reclen;
>>> +    char d_name[1];
>>> +  } kbuf[KBUF_SIZE / sizeof (struct kernel_dirent)];
>> 
>> I think it's still not clear to me in which cases we actually need to
>> move the dirent entries in the buffer.  My impression is that we just
>> need to move d_name by one byte because before, d_type was after the
>> name, and afterwards, it comes before the name.  But the record
>> boundaries are unchanged.
>
> My understanding is the record boundary would be same as long the 
> d_name fits on the alignment padding space minus the size of the
> d_type.  Otherwise the dirent64 will need to be extended.

Hmm.  The problem is mips64 n32, right?  Where unsigned long is 32 bits?

Thanks,
Florian

  reply	other threads:[~2019-08-28 21:23 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 18:31 Adhemerval Zanella
2019-07-31 18:31 ` [PATCH v2 3/5] posix: Optimize stack Linux posix_spawn Adhemerval Zanella
2019-08-28 14:09   ` Adhemerval Zanella
2019-10-07 17:50     ` Adhemerval Zanella
2019-07-31 18:31 ` [PATCH v2 2/5] posix: Add posix_spawn_file_actions_closefrom Adhemerval Zanella
2019-08-28 14:09   ` Adhemerval Zanella
2019-08-28 17:22     ` Joseph Myers
2019-08-28 21:03       ` Adhemerval Zanella
2019-07-31 18:31 ` [PATCH 4/5] linux: Optimize posix_spawn spurious sigaction calls Adhemerval Zanella
2019-08-28 14:09   ` Adhemerval Zanella
2019-08-29  8:38   ` Florian Weimer
2019-08-29 11:26     ` Adhemerval Zanella
2019-08-30 10:07       ` Florian Weimer
2019-08-30 13:05         ` Adhemerval Zanella
2019-09-02 13:14           ` Florian Weimer
2019-09-02 19:47             ` Adhemerval Zanella
2019-10-07 17:51               ` Adhemerval Zanella
2019-10-07 18:25                 ` Christian Brauner
2019-10-07 18:32                   ` Florian Weimer
2019-10-07 21:08                     ` Christian Brauner
2019-10-07 18:35                   ` Adhemerval Zanella
2019-10-07 18:40                     ` Florian Weimer
2019-10-07 19:20                       ` Adhemerval Zanella
2019-10-09  9:37                         ` Florian Weimer
2019-10-09 10:25                           ` Christian Brauner
2019-10-09 12:17                           ` Adhemerval Zanella
2019-10-09 19:16                             ` Florian Weimer
2019-10-07 21:00                     ` Joseph Myers
2019-10-07 18:41                 ` Florian Weimer
2019-07-31 18:31 ` [PATCH v2 5/5] posix: Use posix_spawn for wordexp Adhemerval Zanella
2019-08-28 14:10   ` Adhemerval Zanella
2019-10-07 17:51     ` Adhemerval Zanella
2019-10-07 19:33   ` Florian Weimer
2019-10-07 21:04     ` Carlos O'Donell
2019-10-08  9:58       ` Florian Weimer
2019-10-08 17:41     ` Adhemerval Zanella
2019-10-09  9:11       ` Florian Weimer
2019-10-09 12:18         ` Adhemerval Zanella
2019-08-28 14:09 ` [PATCH v2 1/5] mips: Do not malloc on getdents64 fallback Adhemerval Zanella
2019-08-28 14:35 ` Andreas Schwab
2019-08-28 17:01   ` Adhemerval Zanella
2019-08-28 14:42 ` Florian Weimer
2019-08-28 21:02   ` Adhemerval Zanella
2019-08-28 21:23     ` Florian Weimer [this message]
2019-08-29 11:04       ` Adhemerval Zanella
2019-08-30  9:53 ` Florian Weimer
2019-08-30 12:53   ` Adhemerval Zanella
2019-09-02 12:59     ` Florian Weimer
2019-09-02 17:38       ` Adhemerval Zanella
2019-10-07 17:49         ` Adhemerval Zanella
2019-10-07 18:29         ` Florian Weimer
2019-10-08 17:38           ` Adhemerval Zanella
2019-10-08 18:52             ` Florian Weimer
2019-10-08 19:52               ` Adhemerval Zanella
2019-10-08 19:59                 ` Florian Weimer
2019-10-09 13:02                   ` Adhemerval Zanella
2020-11-02 19:51             ` Joseph Myers
2020-11-02 22:10               ` Adhemerval Zanella
2020-11-03 10:27                 ` Florian Weimer

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=87muft9e7d.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).