public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Anshul Kundra <anshul.kundra@hcl.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: getbmap!!!!!!!
Date: Tue, 06 Mar 2012 17:51:32 -0600	[thread overview]
Message-ID: <4F56A304.8060505@sandeen.net> (raw)
In-Reply-To: <CACBF2D716C5104BAC48A16827DE5B150A220515A6@NDA-HCLT-EVS04.HCLT.CORP.HCL.IN>

On 03/06/2012 11:11 AM, Anshul Kundra wrote:
> To Developers ,
> 
>  
> 
> Please provide me some description regarding the xfs_getbmap what it
> suppose to do , suppose I want to create a fiule and write on it I got
> the inode of file then what fields I will send to the xfs getbmap
> (called via xfs_ioc_getbmapx ) ,

Please see the "XFS_IOC_GETBMAP" section in the xfsctl(3) man page.

-Eric

> -          What fields of getbmapx structure will be initialized  before
> passing in the xfs_ioc_getbmapx ?
> 
> -          What it will do after passing the fields (Function overview
> if possible)
> 
> -          Why the arg+1 is being passed in the xfs_ioc_getbmapx
> 
> I know the reason of formatter
> 
>  
> 
> Xfs_ioc_getbmapx(arguments)
> 
> {
> 
>  
> 
>         Xfs_getbmap();
> 
>         Copy_to_user() ; // why the copying done here as in the function
> itself for every entry it is copying the information into user buffer
> then why outside the function call here it needs the copy again
> 
> }
> 
>  
> 
> Thanks & Best Regards
> 
> Anshul Kundra
> 
> 
> ------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-03-06 23:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 17:11 getbmap!!!!!!! Anshul Kundra
2012-03-06 23:51 ` Eric Sandeen [this message]

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=4F56A304.8060505@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=anshul.kundra@hcl.com \
    --cc=xfs@oss.sgi.com \
    /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