mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guan Xuetao" <guanxuetao@mprc.pku.edu.cn>
To: "'Arnd Bergmann'" <arnd@arndb.de>
Cc: <linux-arch@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] asm-generic headers: modify stat.h in include/asm-generic to be applicable to more architectures
Date: Mon, 10 Jan 2011 21:58:02 +0800	[thread overview]
Message-ID: <005201cbb0ce$65e725f0$31b571d0$@mprc.pku.edu.cn> (raw)
In-Reply-To: <201101090128.25371.arnd@arndb.de>

IMO, asm-generic headers should be used in more architectures as far as possible.
The patch of stat.h could be split into two parts to discuss.
Firstly,  STAT64_HAS_BROKEN_ST_INO is defined in most architecture's asm/stat.h,
and it should be considered as the part in asm-generic/stat.h.
Secondly, STAT64_PAD_BEFORE_* are misunderstanding definitions, and perhaps
it should use STAT64_ST_SIZE_NEED_ALIGN_64.
Indeed, the macros are used for compatibility, but most architectures could make full use of
asm-generic headers, and new architectures could just follow the default values.

Guan Xuetao

> -----Original Message-----
> From: Arnd Bergmann [mailto:arnd@arndb.de]
> Sent: Sunday, January 09, 2011 8:28 AM
> To: Guan Xuetao
> Cc: linux-arch@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] asm-generic headers: modify stat.h in include/asm-generic to be applicable to more architectures
> 
> On Saturday 08 January 2011, Guan Xuetao wrote:
> > From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
> >
> >  This patch modifies stat.h in include/asm-generic to be applicable to more architectures.
> >  STAT64_HAS_BROKEN_ST_INO is defined in most architecture's asm/stat.h, and it need
> >  32-bit __st_ino member to be defined in different position of 64-bit st_ino member.
> >  STAT64_PAD_BEFORE_ST_SIZE is the pad before st_size member, with default value 8 bytes.
> >  STAT64_PAD_BEFORE_ST_BLOCKS is the pad before st_blocks member, with default value
> >  4 bytes to align the following member to 64-bit.
> 
> I'd prefer not to apply this patch. It makes the generic header
> significantly more complex, and I can't see a significant benefit.
> 
> The existing architectures would all still have to define the macros
> you test and also keep defining stuff like __old_kernel_stat, while
> risking to introduce bugs while changing to the common header. We've
> done similar tricks in other places, where the differences between
> architectures are smaller, but this one doesn't seem worth it
> unless we can get to the point where we can define struct stat in
> linux/stat.h for everyone and only do the macros for the architectures
> that need it.
> 
> 	Arnd


  reply	other threads:[~2011-01-10 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 13:23 Guan Xuetao
2011-01-09  0:28 ` Arnd Bergmann
2011-01-10 13:58   ` Guan Xuetao [this message]
2011-01-11  4:40     ` Arnd Bergmann
2011-01-11  8:50       ` Guan Xuetao
     [not found]   ` <lapr25MsLHA.5972@exchange1.tad.internal.tilera.com>
2011-01-17  4:27     ` Chris Metcalf

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='005201cbb0ce$65e725f0$31b571d0$@mprc.pku.edu.cn' \
    --to=guanxuetao@mprc.pku.edu.cn \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®