[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1476703920.2520.105.camel@petrovitsch.priv.at>
Date: Mon, 17 Oct 2016 13:32:00 +0200
From: Bernd Petrovitsch <bernd@...rovitsch.priv.at>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>,
Hannes Reinecke <hare@...e.de>, linux-raid@...r.kernel.org
Cc: Christoph Hellwig <hch@....de>, Guoqing Jiang <gqjiang@...e.com>,
Jens Axboe <axboe@...com>, Joe Perches <coupons@...ches.com>,
Mike Christie <mchristi@...hat.com>,
Neil Brown <neilb@...e.com>, Shaohua Li <shli@...nel.org>,
Tomasz Majchrzak <tomasz.majchrzak@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org, kbuild-all@...org,
ltp@...ts.linux.it
Subject: Re: MD-RAID: Use seq_putc() in three status functions?
On Mon, 2016-10-17 at 13:10 +0200, SF Markus Elfring wrote:
[...]
> > (Which up to now I thought was basic programming knowledge...)
>
> By the way:
> Run time environments still exist where the size of a pointer can
> be also just one byte, don't they?
In the context of the Linux kernel: No.
[ Side note: there might be some DSP out there with a running Linux
kernel which cannot really address a "byte" (meaning 8bits) but only in
register sized quantities (and also aligned for that). But no one cares
here really deeply as that is a so fundamental difference that the C-
compiler must cope with that anyways in the first place. ]
[...]
> > See above. At the moment _any_ test result from your side would do.
>
> I imagine that another single result might not be representative.
Publish not only results but also everything (complete!) so that anyone
can *easily* follow it to check and reproduce the results - especially
if you want people with knowledge of other architectures to comment
(otherwise they probably won't bother).
Kind regards,
Bernd
--
Bernd Petrovitsch Email : bernd@...rovitsch.priv.at
LUGA : http://www.luga.at
Powered by blists - more mailing lists