Hi All,
I need to know if there are some differences, in performances, between
a ext2 filesystem in a 10Gb partition and another that reside in a 130Gb,
each one have 4Kb block size.
I'm configuring a Compaq ML350 2x800PIII, 1Gb RAM, 5x36Gb UWS3 RAID 5
with Smart Array 4300, as database SQL serv
At 19.00 21/11/00 +0100, Jakob Østergaard wrote:
>On Tue, Nov 21, 2000 at 05:58:58PM +0100, Roberto Fichera wrote:
> > Hi All,
> >
> > I need to know if there are some differences, in performances, between
> > a ext2 filesystem in a 10Gb partition and another that resi
I'm receiving duplicated email from Linux-Kernel, Linux-Net and Linux-SMP.
There's some problems ?
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
At 11.10 23/10/00 +0300, Matti Aarnio wrote:
>On Mon, Oct 23, 2000 at 10:56:15AM +0100, Roberto Fichera wrote:
> > I'm receiving duplicated email from Linux-Kernel, Linux-Net and Linux-SMP.
> > There's some problems ?
>
>Yes, yours. Double subscription. (E
At 21.29 08/12/00 +0100, Rasmus Andersen wrote:
>Hi.
>
>The following patch moves the page_table_lock in mm/* to cover the
>modification of mm->rss in 240-test12-pre7. It was inspired by a
>similar patch from davej(?) which covered too much, AFAIR. The item
>is on Tytso's ToDo list.
[...snip...]
At 13.43 09/12/00 +0100, Rasmus Andersen wrote:
>On Sat, Dec 09, 2000 at 11:25:09AM +0100, Roberto Fichera wrote:
>[...]
> > >+ spin_lock(&mm->page_table_lock);
> > > mm->rss++;
> > >+ spin_unlock(&mm->page_table_lock);
>
At 06.42 09/12/00 -0800, David S. Miller wrote:
>Date: Sat, 09 Dec 2000 15:48:05 +0100
>From: Roberto Fichera <[EMAIL PROTECTED]>
>
>>atomic_t does not guarentee a large enough range necessary for mm->rss
>
>If we haven't some atomic_t t
At 07.00 09/12/00 -0800, David S. Miller wrote:
>Date: Sat, 09 Dec 2000 16:07:03 +0100
>From: Roberto Fichera <[EMAIL PROTECTED]>
>
>8 bits for a spinlock ? What kind of use we have here ?
>
>Sparc32 (like some other older architectures) do not have a
>wor
Hi all,
Does anyone know how to configure this controller (chipset AAA-133U2 aka
AIC-78xx)
with one RAID5 hardware volume ? The kernel 2.2.16 see all the disks
(4x18Gb) but
don't see the unique volume.
Thanks in advance.
Roberto Fichera.
-
To unsubscribe from this list: send the
que volume.
>
>These boards are not currently supported in RAID mode. Your
>best bet is Linux MD.
Ok! As I was thinking, I must configure it with Linux MD.
Thanks.
Roberto Fichera.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
)):
ext2_write_inode: unable to read inode block - inode=1553880, block=3112978
It's a disk error or a FS error ? What can I do to fix the problem ? I
500Km distant from this machine :-(
and I want made some check remotely before reboot it.
Any suggestion ?
Thanks in advance.
Roberto Fichera.
be also interesting to
define _externally_ the mapping of the reason so the
userspace tool could handle it easily.
Roberto Fichera.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
At 19.35 18/01/2008, Arjan van de Ven wrote:
>Roberto Fichera wrote:
>> At 18.36 18/01/2008, Arjan van de Ven wrote:
>>> The Intel Open Source Technology Center is pleased to announce the
>>> release of version 0.1 of LatencyTOP, a tool for developers to vis
29 spargi kernel: [] _sinittext+0x15a/0x15e
Feb 16 13:06:29 spargi kernel:
Roberto Fichera.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
3217x_ssi_setup: SSI_STMSK=0x00fc,SSI_SRMSK=0x00fc
si3217x_ssi_set_clock: BIT_CLK=53248000
Finally the SSI1 registers are set like this:
ssi_scr=0x00bf
ssi_sier=0x01d005f5
ssi_stcr=0x02e8
ssi_srcr=0x0288
ssi_stccr=0x0000670b
ssi
On 03/29/2016 07:31 PM, Tim Harvey wrote:
> On Tue, Mar 29, 2016 at 9:44 AM, Roberto Fichera wrote:
>>>
>>> Roberto,
>>>
>>> What board/platform is this and what does /proc/interrupts look like?
>> It's a custom board
>>
>> root
On 03/30/2016 12:10 PM, Arnd Bergmann wrote:
> On Wednesday 30 March 2016 10:00:33 Roberto Fichera wrote:
>>> Check your XIO2001 routing and insure the following for proper IRQ mapping:
>>> Slot12: IDSEL A28: socket INTA = XIO2001 INTA
>>> Slot13: IDSEL A29: socket
On 03/30/2016 03:38 PM, Tim Harvey wrote:
> On Wed, Mar 30, 2016 at 5:50 AM, Roberto Fichera wrote:
>> On 03/30/2016 12:10 PM, Arnd Bergmann wrote:
>>> On Wednesday 30 March 2016 10:00:33 Roberto Fichera wrote:
>>>>> Check your XIO2001 routing and in
On 03/29/2016 05:10 PM, Tim Harvey wrote:
> Arnd,
>
> Right, on the IMX the MSI interrupt is GIC-120 which is also the
> legacy INTD and I do see that if I happen to put a radio in a slot
> where due to swizzling its pin1 becomes INTD (GIC-120) the interrupt
> does fire and the device works. Any ot
On 03/29/2016 06:40 PM, Tim Harvey wrote:
> On Tue, Mar 29, 2016 at 9:13 AM, Roberto Fichera wrote:
>> On 03/29/2016 05:10 PM, Tim Harvey wrote:
>>> Arnd,
>>>
>>> Right, on the IMX the MSI interrupt is GIC-120 which is also the
>>> legacy INTD and
20 matches
Mail list logo
