[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49395329523DD64492581B505F80C86D5A5BCD38EA@EXMAIL.ad.emulex.com>
Date: Fri, 18 Mar 2011 14:52:16 -0700
From: <Ajit.Khaparde@...lex.Com>
To: <bhutchings@...arflare.com>
CC: <netdev@...r.kernel.org>
Subject: RE: [RFC] ethtool: Display reg dump length via get driver info.
______________________________________
From: Ben Hutchings [bhutchings@...arflare.com]
Sent: Friday, March 18, 2011 4:32 PM
To: Khaparde, Ajit
Cc: netdev@...r.kernel.org
Subject: Re: [RFC] ethtool: Display reg dump length via get driver info.
On Fri, 2011-03-18 at 16:06 -0500, Ajit Khaparde wrote:
>> Devices like BE store Reg Dump Data in the hardware.
> Where else would it be?
Well yes. That's true.
>> This change will allow to just peek into the hardware
>> to see if any data is available for a dump and analysis,
>> without actually dumping the register data.
> [...]
> This is wrong. ethtool_ops::get_regs_len really should return a
> constant, otherwise ethtool (and the kernel) cannot allocate a buffer of
> the right size. If the size of a dump really does vary then make it
> return the maximum possible size for the device.
Yes, it is a constant size. And will always be the max size possible.
I just want to see if I can get the length, without really making the ethtoool -d call.
Because that will trigger the dump too.
At that moment, I may not be interested in the data itself.
-Ajit
> Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists