Re: [Iscsitarget-devel] IET on mips, big-endian

[Ross S. W. W. <RW...@me...>]

On Jun 15, 2011, at 9:23 PM, "iet iscsi" <iet...@gm...> wrote:

> Hi Ross,
>  
> I agree - it might not be IET code issue. But, wanted to understand as to what is the relation between Number of Sectors in nullio (i.e. nullio volume size) and load on the system. I would appreciate if you could please shed some light on this.

The number of sectors you set in nullio is simply the number of sectors that is reported to the initiator for the nullio lun.

All IO sent to the lun is discarded and all IO read from the lun is whatever kalloc returns, basically random kernel bytes.

So the only problem I could see is setting a number of sectors so big that READ_CAPACITY16 can't handle it.


> Thanks for your time and help.
> 
> On Wed, Jun 15, 2011 at 3:31 PM, Ross S. W. Walker <RW...@me...> wrote:
> 
> The reason I ask is cause these kernel oops messages are coming from the TCP module.
> 
> Maybe your NAPI driver has an IRQ problem with kernel API? Very easy to mess up IRQ handling in drivers.
> 
> -Ross
> 
> 
> On Jun 15, 2011, at 6:28 PM, "iet iscsi" <iet...@gm...> wrote:
> 
>> Hi Ross,
>>  
>> This is our inhouse ethernet driver (napi based).
>>  
>> Thanks for your time and help.
>> 
>> On Wed, Jun 15, 2011 at 3:24 PM, Ross S. W. Walker <RW...@me...> wrote:
>> On Jun 15, 2011, at 9:48 AM, "iet iscsi" <iet...@gm...> wrote:
>> 
>> > CRASH #2:
>> > WARNING: at net/ipv4/tcp.c:1457 tcp_recvmsg+0x7c0/0x990()
>> > recvmsg bug 2: copied 8D07C2AD seq 1EAA6653 rcvnxt 8D083A71 fl 4000
>> > Modules linked in: iscsi_trgt test_ethernet ipv6
>> 
>> What is "test_ethernet"?
>> 
>> -Ross
>> 
>> ______________________________________________________________________
>> This e-mail, and any attachments thereto, is intended only for use by
>> the addressee(s) named herein and may contain legally privileged
>> and/or confidential information. If you are not the intended recipient
>> of this e-mail, you are hereby notified that any dissemination,
>> distribution or copying of this e-mail, and any attachments thereto,
>> is strictly prohibited. If you have received this e-mail in error,
>> please immediately notify the sender and permanently delete the
>> original and any copy or printout thereof.
>> 
>> 
> ______________________________________________________________________
> This e-mail, and any attachments thereto, is intended only for use by
> the addressee(s) named herein and may contain legally privileged
> and/or confidential information. If you are not the intended recipient
> of this e-mail, you are hereby notified that any dissemination,
> distribution or copying of this e-mail, and any attachments thereto,
> is strictly prohibited. If you have received this e-mail in error,
> please immediately notify the sender and permanently delete the
> original and any copy or printout thereof.
> 
______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.